This message was deleted.
# typescripts
sparse-intern-71089
03/19/2021, 8:02 PMThis message was deleted.
r
red-match-15116
03/19/2021, 8:04 PMCan you escape the
$m
millions-furniture-75402
03/19/2021, 8:05 PMsame error
f
faint-table-42725
03/19/2021, 9:26 PMI would not expect
db$faint-table-42725
03/19/2021, 9:28 PMIf so, would love to get that fixed. But I would try without the
db$m
millions-furniture-75402
03/22/2021, 1:54 PMfor reference, this database was created using the custom ComponentResource provided in this example: https://github.com/pulumi/examples/blob/master/aws-stackreference-architecture/database/src/database.ts#L76
millions-furniture-75402
03/22/2021, 1:55 PMFor our Disaster Recovery Test, we took a snapshot of our RDS Instance, and copied it to a new region, then created a new RDS Instance in the AWS Web Console with the snapshot.
Then we ran our base-infrastructure with everything except the RDS Instance which is a child of the DB ComponentResource. Then tried to import it.
millions-furniture-75402
03/22/2021, 1:57 PMWe did find that we can use Pulumi to use a snapshot when creating an RDS Instance, so we’ll take that approach next. However, using this custom ComponentResource has left us feeling like we’ve painted ourselves into a corner a little bit when it comes to importing infrastructure for this particular use case of import which I understand is different than the usual case.
millions-furniture-75402
03/22/2021, 3:30 PMPassing
snapshotIdentifierf
faint-table-42725
03/22/2021, 11:16 PMThanks for explaining. I think generally speaking, we’ll want to make importing `ComponentResource`s more straightforward. One thing you could try (which is more complex than the
snapshotIdentifierimportComponentResourcem
millions-furniture-75402
03/23/2021, 1:01 PMThat is an interesting thought. We do have other custom ComponentResources if the need arises.
10 Views