magnificent-soccer-44287
02/24/2024, 6:24 PMconst dockerImage = new docker.Image('pulumiDockerImage', { build: {}, ... }, { dependsOn: [someNetworkingResource], changeset: ['fargate'] }
ā¢ This could be made, for example, to only update the resources tagged in current changeset as well as their downstream and upstream chain of "dependsOn" related resources.
We've gotten into a pattern of splitting stacks in often logically/architecturally sub-optimal ways to manage our individual deployment scope, speed, complexity.
This may involve notable design consideration/rigor to pull of in a safe manner but I do think it would be a feature valuable to MANY customers.
Especially if it was coupled with a folder and file based 'checksum' resource to control what changesets should be automatically applied. For example:
const fargateRelatedGitRepoFiles = new pulumi.Changeset('pulumiChangeset', { name: 'fargate', includedFiles: [WHITELIST], excludedFiles: [BLACKLIST] })
Additional food for thought implementation pattern:
ā¢ Create pulumi.Changeset resource -> only update things that list it in their 'dependsOn' as well as their upstream and downstream 'dependsOn' chains (eliminate CLI flags entirely)
ā¦ For example, if no defined changeset is active, we could just fall back to deploying everything (once again consideration/rigor design choice to be fleshed out)little-cartoon-10569
02/25/2024, 1:00 AMmagnificent-soccer-44287
02/25/2024, 6:22 AMmagnificent-soccer-44287
02/25/2024, 6:23 AMmagnificent-soccer-44287
02/25/2024, 6:24 AM