VPC report bucket name isn't unique enough #148
Assignees
Comments
jce-redhat
added a commit
that referenced
this issue
May 15, 2024
* create a unique deployment ID stored in {{ playbook_dir }}/.deployment_id
* override VPC report bucket name to include deployment ID
Closes #148
|
+1 I noticed this error as well. |
jce-redhat
added a commit
that referenced
this issue
May 20, 2024
* create a unique deployment ID stored in {{ playbook_dir }}/.deployment_id
* override VPC report bucket name to include deployment ID
Closes #148
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we're leveraging playbooks and roles from the aws.infrastructure_config_demos repo for a number of the cloud-related demos. one job template creates a VPC report and writes it to a bucket, but that bucket name isn't unique enough to guarantee that it doesn't already exist globally. i've created two demo environments today where the bucket already exists, and the VPC report job template fails because it doesn't have write access to the bucket.
a generalized way of approaching this would be to generate a random deployment ID for each product-demos deployment, then use that ID as part of the bucket name. the ID could be used in future tasks where some unique identifier is required.
The text was updated successfully, but these errors were encountered: