-
-
Notifications
You must be signed in to change notification settings - Fork 1
[Meta] Handle settings drift #1
Comments
It looks like this may not be entirely possible: pulumi/pulumi-github#160 I think we might be able to do something with import that diffs against existing imported files, as long as we don't touch them manually. |
It looks like this may not be entirely possible: pulumi/pulumi-github#160 I'm attempting to do something using the |
I've got something just about working. I had to use a PAT (I used CukeBot's) to be able to fetch the list of teams from GitHub's API to generate the resources list for the import. There's now a job failing as there's been a teeny bit of drift I guess since I last ran the import. To do:
|
It does look like the I guess we need to either just use a temporary file-based stack, or create a new stack for each import. |
I've changed it over to use a file-based stack. I also learned that the generated ts files don't seem to always be in a consistent order, so checking them isn't going to work. I'm attempting to use |
It's going to be difficult to use this until pulumi/pulumi-github#168 is fixed. |
Any of the settings being handled by these scripts could be changed manually. How do we handle when the actual settings have drifted away from what's declared here in this repo?
Scenarios:
Maintain
access for thecore
team. We bring it under management of these scripts, but that's not defined in the config scripts. Will that access be removed when the config is applied?The text was updated successfully, but these errors were encountered: