This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
Use AMI from mappings #11
Open
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
a6200f1
to
886e02d
Compare
9863c7b
to
31566a9
Compare
We still need the parameter ** ManagerImageId** for our custom patched AMI amzn2 😞 Is there a possibility for a condition, to mix in the mapping, if an image id is not given? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR removes the CloudFormation parameter that forced you to specify an AMI ID for manager instance.
Latest AMIs for AWS regions are obtained with
make list-latest-amisand are present in the template as a Mapping. The AMI is then selected automatically by CloudFormation based on the AWS Region the stack is launched in.This resolves #6.