-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document creating stacker bucket with CloudFormation. #571
base: master
Are you sure you want to change the base?
Conversation
Hey @troyready / @GarisonLotus. This is a slightly more generalized version of what we do internally. Eventually, I'd like to support automating this more in the config, like I talk about in #497 (comment), but it's probably worth documenting that his method can be used already. |
ServerSideEncryptionConfiguration=[aes])) | ||
|
||
def create_template(self): | ||
self.template.add_resource(self.bucket) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably have the bucket name as an output.
@@ -0,0 +1,33 @@ | |||
from stacker.blueprints.base import Blueprint | |||
|
|||
from troposphere import Ref |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd replace Ref
with NoValue
and just use that later, since that's the only use of Ref.
an existing bucket in a different region, you can set the | ||
**stacker_bucket_region** to the region where you want to create the bucket. | ||
|
||
Alternatively, if you'd like to have more control over creation of the stacker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe mention that if they want more control over creation of the bucket, they can use the Bucket
blueprint from stacker_blueprints
as well.
As talked about in #497 (comment), this documents how more advanced stacker users might setup a stacker bucket, when they want more control over creation of the bucket (e.g. tags, default encryption, bucket policies, created in a specific AWS account or region, etc).