Skip to content
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

Merged
merged 1 commit into from
Apr 16, 2024

Conversation

nicolas2bert
Copy link
Contributor

@nicolas2bert nicolas2bert commented Jan 16, 2024

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

@bert-e
Copy link
Contributor

bert-e commented Jan 16, 2024

Hello nicolas2bert,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jan 16, 2024

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@nicolas2bert nicolas2bert changed the title S3UTILS-54 crrExistingObjects handles both S3C and Artesca S3UTILS-54 crrExistingObjects is compatible with both S3C and Artesca Jan 16, 2024
@nicolas2bert nicolas2bert force-pushed the improvement/S3UTILS-54/merge2 branch 2 times, most recently from b42df13 to b0e964c Compare January 16, 2024 15:08
@nicolas2bert nicolas2bert changed the base branch from development/1.14 to development/1.15 February 20, 2024 09:55
@bert-e
Copy link
Contributor

bert-e commented Feb 20, 2024

Incorrect fix version

The Fix Version/s in issue S3UTILS-54 contains:

  • 1.14.5

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 1.15.0

Please check the Fix Version/s of S3UTILS-54, or the target
branch of this pull request.

Copy link
Contributor

@anurag4DSB anurag4DSB left a 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)

CRR/ReplicationStatusUpdater.js Outdated Show resolved Hide resolved
@bert-e
Copy link
Contributor

bert-e commented Feb 20, 2024

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

process.exit.mockReset();

// Clear the mocks before each test
// ReplicationStatusUpdater.mockClear();
Copy link
Contributor

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.
@nicolas2bert
Copy link
Contributor Author

@bert-e approve

@bert-e
Copy link
Contributor

bert-e commented Apr 16, 2024

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/1.15

The following branches have NOT changed:

  • development/1.13
  • development/1.14
  • development/1.4

Please check the status of the associated issue S3UTILS-54.

Goodbye nicolas2bert.

The following options are set: approve

@bert-e bert-e merged commit 1cf6c9d into development/1.15 Apr 16, 2024
10 checks passed
@bert-e bert-e deleted the improvement/S3UTILS-54/merge2 branch April 16, 2024 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants