-
Notifications
You must be signed in to change notification settings - Fork 2
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
S3UTILS-54 crrExistingObjects is compatible with both S3C and Artesca #305
Conversation
Hello nicolas2bert,My role is to assist you with the merge of this Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
b42df13
to
b0e964c
Compare
b574630
to
13f9153
Compare
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
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, thanks for the context on CS and BB.
As this is a breaking change for Artesca, and XDM, we should create a follow up ARTESCA ticket for the same(may be already handled/discussed)
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
13f9153
to
76e23ec
Compare
tests/unit/CRR/crrExistingObjects.js
Outdated
process.exit.mockReset(); | ||
|
||
// Clear the mocks before each test | ||
// ReplicationStatusUpdater.mockClear(); |
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.
Is this needed?
!! Warning !! : Breaking change for Zenko deployment only (XDM and Artesca): introduction of mandatory environment variables ACCESS_KEY, SECRET_KEY, and ENDPOINT The Pull Request introduces these key changes: Switch to S3 and Backbeat API: crrExistingObjects now uses S3 and Backbeat APIs instead of direct metadata calls, enhancing security and maintainability but potentially slowing down performance due to added abstraction. It's expected to be minor, but will undergo testing. Refactoring for testability: The script has been refactored to make it more modular and easier to test, improving code clarity and allowing for better unit/functional testing. Adding unit/functional tests with mocks: Unit/functional tests using mocked S3 and Backbeat APIs have been added, providing a controlled environment for more comprehensive and reliable testing of the script's functionality.
76e23ec
to
1cf6c9d
Compare
@bert-e approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue S3UTILS-54. Goodbye nicolas2bert. The following options are set: approve |
The Pull Request introduces these key changes:
Switch to S3 and Backbeat API: crrExistingObjects now uses S3 and Backbeat APIs instead of direct metadata calls, improving security and maintainability but potentially slowing down performance due to added abstraction. It's expected to be minor, but will undergo testing.
Refactoring for testability: The script has been refactored to make it more modular and easier to test, improving code clarity and allowing for better unit/functional testing.
Adding unit/functional tests with mocks: Unit/functional tests using mocked S3 and Backbeat APIs have been added, providing a controlled environment for more comprehensive and reliable testing of the script's functionality.
Note: Additional modifications are required in both CloudServer and Backbeat:
https://scality.atlassian.net/browse/CLDSRV-501
https://scality.atlassian.net/browse/BB-483
!! Warning !! : Breaking change for Zenko deployment only (XDM and Artesca): introduction of mandatory environment variables ACCESS_KEY, SECRET_KEY, and ENDPOINT