This message was deleted.

There is definitely a way to go about this, although it isn't as straightforward as we would like. For example, if you create a checkpoint with all the right URNs and IDs, then

pulumi refresh

will read everything back. We are discussing an

import

command that automates this: https://github.com/pulumi/pulumi/issues/1635. In the absence, @white-balloon-205 or @microscopic-florist-22719 may have tips.

I don’t yet have a mental model of the state internals, so attempting this makes manually me a bit nervous at this stage

Yes,

pulumi stack export

will dump it to stdout, and

pulumi stack import

will re-read it from stdin. (Although we track history, we don't have great support for going back in time to get historical checkpoints, so I'd recommend backing things up before manual edits.)

i’m usually not a fan of interactive things, as they make automation harder, but i think it is appropriate here, since this is inherently a one-off task, not something to be automated

Just so I understand, you're saying you'd want to write your program, then instead of

pulumi up

, you'd say

pulumi import

and it'd compute the resources and then let you pick resources from your current AWS account to form the checkpoint state? Basically, adopting them one at a time?

yeaaaaah - i think so … this is just a random idea

I like it 🙂

so i basically made this pulumi script by copying the existing manual deployment

The nice thing about this is that it could warn you and/or help you reconcile if your program couldn't possibly have produced the state you're adopting.

the reason my mind went to interactive is b/c you have a lot of info to drive the process - like you know resource types and the like, so you can provide good choices to match things up

Sort of like an interactive merge (take theirs, take mine, etc)

yeah - i think you need to support “merge markers” of some kind in your snapshot files too

I like this approach better than what we'd previously discussed, which was more of a "start from nothing and start importing". This is difficult, but with the interactive, program-first standpoint, at least -- as you say -- you know what you're trying to find (types, etc). So it actually seems feasible. /cc @microscopic-florist-22719 and @lemon-spoon-91807 as I think be keen on this

just testing my mental model: urn == arn on aws, yes?

URN is assigned by Pulumi, actually.

oh, hm

ID is the AWS identifier, often the ARN, but it depends on the resource type.

got it - how would i figure out URNs then for a manual reconciliation?

This is an S3 Bucket:

{
                "urn": "urn:pulumi:joe-thumbnailer::video-thumbnailer::cloud:bucket:Bucket$aws:s3/bucket:Bucket::bucket",
                "custom": true,
                "id": "bucket-e2ed56f",
                "type": "aws:s3/bucket:Bucket",
                "inputs": {
                    "acl": "private",
                    "bucket": "bucket-e2ed56f",
                    "forceDestroy": true,
                    "serverSideEncryptionConfiguration": {
                        "rule": {
                            "applyServerSideEncryptionByDefault": {
                                "sseAlgorithm": "AES256"
                            }
                        }
                    }
                },
                "outputs": {
                    "accelerationStatus": "",
                    "acl": "private",
                    "arn": "arn:aws:s3:::bucket-e2ed56f",
                    "bucket": "bucket-e2ed56f",
                    "bucketDomainName": "<http://bucket-e2ed56f.s3.amazonaws.com|bucket-e2ed56f.s3.amazonaws.com>",
                    "bucketRegionalDomainName": "<http://bucket-e2ed56f.s3.us-west-2.amazonaws.com|bucket-e2ed56f.s3.us-west-2.amazonaws.com>",
                    "corsRules": [],
                    "forceDestroy": true,
                    "hostedZoneId": "Z3BJ6K6RIION7M",
                    "id": "bucket-e2ed56f",
                    "loggings": [],
                    "region": "us-west-2",
                    "requestPayer": "BucketOwner",
                    "serverSideEncryptionConfiguration": {
                        "rule": {
                            "applyServerSideEncryptionByDefault": {
                                "kmsMasterKeyId": "",
                                "sseAlgorithm": "AES256"
                            }
                        }
                    },
                    "tags": {},
                    "versioning": {
                        "enabled": false,
                        "mfaDelete": false
                    }
                },
                "parent": "urn:pulumi:joe-thumbnailer::video-thumbnailer::cloud:bucket:Bucket::bucket",
                "dependencies": [],
                "initErrors": null,
                "provider": "urn:pulumi:joe-thumbnailer::video-thumbnailer::pulumi:providers:aws::default::5532a60a-758b-4589-bddb-98f4670e6fb9"
            },

hm yeah - pretty cumbersome

Nice! 👍

Thanks