-
Notifications
You must be signed in to change notification settings - Fork 252
Ft/more s3 locations support #1207
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
Conversation
0dd2a45 to
fdabde3
Compare
|
PR has been updated. Reviewers, please be cautious. |
fdabde3 to
4011d20
Compare
|
PR has been updated. Reviewers, please be cautious. |
philipyoo
left a comment
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.
lgtm, but may need to consider using a different whatwg url lib
lib/management.js
Outdated
| @@ -1,3 +1,4 @@ | |||
| const { URL } = require('url'); | |||
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 don't think url.URL is supported in Node v6. Instead there is a property: url.Url but it doesn't seem to work as intended.
Based on this blog: https://www.contentful.com/blog/2016/11/02/node-v7-urls-deprecations-warnings-and-developer-experience/
Looks like support was added in v7?
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.
https://nodejs.org/docs/latest-v6.x/api/url.html#url_the_whatwg_url_api
it is also added in 6.13
jonathan-gramain
left a comment
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.
one style comment, but it looks good to me
| break; | ||
| case 'location-do-spaces-v1': | ||
| case 'location-scality-ring-s3-v1': | ||
| pathStyle = true; // fallthrough |
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 would recommend not relying on fallthrough capability of switch, instead using a map of properties per location name ({ 'location-scality-bleh': { pathStyle: true, ...} }) would be more readable and less error-prone.
|
@ironman-machine try |
|
Hello @alexanderchan-scality "try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/21189' with the following env. args: {
"DEFAULT_BRANCH": "master",
"SCALITY_INTEGRATION_BRANCH": "ultron/master",
"REPO_NAME": "S3",
"SCALITY_S3_BRANCH": "ft/more-s3-locations-support"
}"RUN_BACKBEAT_CRR_TESTS=true": Success |
|
@ironman-machine |
|
Hello @alexanderchan-scality "RUN_BACKBEAT_CRR_TESTS=true": Success {
"DEFAULT_BRANCH": "master",
"SCALITY_INTEGRATION_BRANCH": "ultron/master",
"REPO_NAME": "S3",
"SCALITY_S3_BRANCH": "ft/more-s3-locations-support",
"RUN_BACKBEAT_CRR_TESTS": "true"
} |
c30f901
4011d20 to
c30f901
Compare
|
PR has been updated. Reviewers, please be cautious. |
c30f901 to
fb2a823
Compare
|
PR has been updated. Reviewers, please be cautious. |
| break; | ||
| case 'location-do-spaces-v1': | ||
| case 'location-scality-ring-s3-v1': | ||
| pathStyle = true; // fallthrough |
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.
Reporting the style comment about using a mapping object rather than relying on fallthrough of a switch.
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.
It's a good cleanup, we'll follow up on it
7409532
|
PR has been updated. Reviewers, please be cautious. |
|
7409532 to
09a5f3d
Compare
|
PR has been updated. Reviewers, please be cautious. |
09a5f3d to
bf3a60f
Compare
|
PR has been updated. Reviewers, please be cautious. |
bf3a60f to
460dd0d
Compare
|
PR has been updated. Reviewers, please be cautious. |
Adds more support options for S3 location constraints: