Enabling "DeployUI" option breaks bucket configuration
See original GitHub issueEnabling the “DeployUI” option results in a broken deployment:
- It ignores the bucket name you entered, and instead creates a new bucket (some-name-demowebsitebucket-hosqmacrnrj8)
- the relevant options point to the created bucket, not the specified one:
TC_AWS_LOADER_BUCKET
- S3 read policies
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Enabling "DeployUI" option breaks bucket configuration #84
Enabling the "DeployUI" option results in a broken deployment: It ignores the bucket name you entered, and instead creates a new bucket ......
Read more >Stack failure options - AWS CloudFormation
On the Configure stack options page, you can set additional options for your stack. For Stack failure options, select Preserve successfully provisioned ...
Read more >How to use GitLab CI to deploy to multiple environments
To install awscli we need pip , which is a tool for Python ... GitLab has a special place for secret variables: Settings...
Read more >Uniform bucket-level access | Cloud Storage
When you enable uniform bucket-level access on a bucket, Access Control Lists (ACLs) are disabled, and only bucket-level Identity and Access Management (IAM) ......
Read more >S3 repository | Elasticsearch Guide [8.5] | Elastic
Here is an example policy which will allow the snapshot access to an S3 bucket named "snaps.example.com". This may be configured through the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi all. We’re currently in the process of updating this solution and have identified several ways to mitigate this issue in the next version. Thanks for your patience/feedback on this matter. Stay tuned!
@groverlalit:
But it doesn’t work this way (currently). If you set the ‘DeployUI’ value to ‘Yes’, the bucket you provide is totally ignored.
Also I’m pretty sure it didn’t work like this in previous versions…it simply added the
serverless-image-handler-ui
folder to your provided bucket, which seems to make alot more sense to me…