Share the snapshots of private stemcells #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpalermo
requested review from
a team,
cunnie and
ramonskie
and removed request for
a team
rkoster
approved these changes
May 16, 2024
|
Thanks! @max-soe |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is currently a bug for shared stemcells. AWS changed the behaviour by copy AMIs to other regions.
The new default is that they only share the AMI now. The snapshot is not shared. As bosh need the snapshot to create it's own AMI, we must share this as well.
With this PR we share the snapshot with the configured accounts and tag them correctly.