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

530: Adds S3 Get and Put ObjectTagging to restore_object_role_policy #531

Conversation

paulpilone
Copy link
Contributor

Summary of Changes

Addresses #530. A wildcard was removed from the GetObject and PutObject actions in restore_object_role_policy which implicitly removed the GetObjectTagging and PutObjectTagging actions. These actions are required for CopyObject and must be now added explicitly.

I targeted the release-10.0.0-beta branch here but feel free to adjust if it should be a different branch.

Changes

  • Adds s3:GetObjectTagging and s3:PutObjectTagging to copy archive source buckets which are required for the S3 CopyObject command.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests (unit, integration, ad-hoc, or otherwise) that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

This was manually tested via the Cumulus Core integration tests. Previous testing was against cumulus-orca v9.0.4. When testing the same integration test against v10.0.0-beta the test failed with an s3 AccessDenied because these actions were implicitly removed.

Verified with a simple CopyObject command using the restore_object_role in a Lambda function.

Copy link
Contributor

@rizbihassan rizbihassan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also update our changelog to note the changes?

https://github.com/nasa/cumulus-orca/blob/release-10.0.0-beta/CHANGELOG.md#changed

@paulpilone
Copy link
Contributor Author

Ah! Sorry about that! Added this change to the mentioned section of the change log. I linked to the GH issue so I hope that's ok. If there's a specific ORCA ticket for this I'm happy to change that.

@paulpilone
Copy link
Contributor Author

It looks like VSCode formatted the CL on save which removed trailing white spaces and resulted in a bigger diff than needed. If that's an issue yell and I'll revert it. Otherwise I'll leave it as is since it's just getting rid of white space.

Copy link
Contributor

@rizbihassan rizbihassan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@paulpilone
Copy link
Contributor Author

@rizbihassan Thanks!

I'm going to be on PTO next week and wanted to ask if there's a timeline for this getting merged into the v10.0.0-beta release? I don't think it's a huge rush for us but I want to update the status on https://bugs.earthdata.nasa.gov/browse/CUMULUS-3768 before I head out in case someone else picks it up.

@rizbihassan
Copy link
Contributor

@rizbihassan Thanks!

I'm going to be on PTO next week and wanted to ask if there's a timeline for this getting merged into the v10.0.0-beta release? I don't think it's a huge rush for us but I want to update the status on https://bugs.earthdata.nasa.gov/browse/CUMULUS-3768 before I head out in case someone else picks it up.

@zroehrich can you approve the PR so that we can merge it?

Copy link
Contributor

@zroehrich zroehrich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@rizbihassan rizbihassan merged commit 1dd7b47 into nasa:release-10.0.0-beta Sep 17, 2024
2 checks passed
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.

3 participants