-
Notifications
You must be signed in to change notification settings - Fork 126
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
fix: Deploy bucket in configured location #227
Conversation
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.
@Gnucki thank you, it looks good (I assume you've tested that it fixes the issue?)
I've proposed one minor style improvement
package/lib/prepareDeployment.js
Outdated
const newBucket = _.cloneDeep(bucket); | ||
newBucket.name = name; | ||
if (location) { | ||
newBucket.properties = newBucket.properties || {}; |
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.
Let's write it as if (!newBucket.properties) newBucket.properties = {}
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.
Improvement done.
Of course, I tested it ;)
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.
Thank you @Gnucki 👍
When will the next release be available with this fix? |
@curtismenmuir just published v3.1.1 |
@medikoo Perfect, thank you :) |
This is a basic correction for the issue #226
Tell me if I can do something better !
Note that this PR is similar to #220