fixed issue with bucket name not being determined #45
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
|
@crsimmons @DanielJonesEB - Let me know if there's anything else required to get this reviewed. Thanks in advance for all of your help! |
|
@crsimmons @DanielJonesEB - Anything else required to get this fix out to all users? Thanks in advance for all of your help! |
|
Makes sense to me. Sorry it took so long to get to it. We had some issues causing our pipeline to fail and everyone at EngineerBetter has been busy with customers. I've taken some time today to try to clean things up. Thanks for your patience! |
|
No worries at all, @crsimmons! Thank you so much for your help! |
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.
Problem: Bucket name could not be determined.
Error: error ensuring config bucket exists before deploy: [error determining if bucket [] exists: [InvalidParameter: 1 validation error(s) found.
Note: This has been tested out and resolved our issues internally.
Fixes #27