This message was deleted Pulumi Community #aws

Join Slack

This message was deleted.

# aws

sparse-intern-71089

07/06/2021, 9:02 PM

This message was deleted.

brave-planet-10645

07/06/2021, 9:47 PM

So are you looking to create the table in the beginning and enable point in time or if you lose it, refill the table then enable point in time?

victorious-megabyte-32350

07/06/2021, 10:39 PM

I have a table already with pitr (I created with pulumi) . If the table for some reason (a bad fix) mess up the data I need restore the table at certain time. I saw pitr, but aws says you need to create a new one.

Copy code

aws dynamodb restore-table-to-point-in-time \
    --source-table-name Music \
    --target-table-name MusicEarliestRestorableDateTime \
    --no-use-latest-restorable-time \
    --restore-date-time 1519257118.0

victorious-megabyte-32350

07/06/2021, 10:40 PM

So the new table is created (outside pulumi)

victorious-megabyte-32350

07/06/2021, 10:41 PM

And I need a way to tell pulumi that there’s a new table

victorious-megabyte-32350

07/06/2021, 10:44 PM

So I can activate the pitr in the new table. I saw the pulumi import, but not sure if the right command to solve the problem. And Idk how to use it to Dynamo (there is only a s3 example)

victorious-megabyte-32350

07/08/2021, 4:19 PM

I'm facing this issue right now. I'm creating a new table in dyanmodb (part of the

point in time recovery

) The table

MusicTableMinutesAgo

(for example) has two properties in the creation (Partition Key

pk

and a Sort Key

sk

). I'm doing a

pulumi import aws:dynamodb/table:Table basic-table MusicTableMinutesAgo

and I'm getting this:

Copy code

all attributes must be indexed. Unused attributes ["sk"]

Is there a status regarding this situation? I saw an issue on github with the same problem https://github.com/pulumi/pulumi/issues/6690

Open in Slack

Previous Next