-
Notifications
You must be signed in to change notification settings - Fork 7
Playbook and Role to move objects from one storage bucket into another #4
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
base: main
Are you sure you want to change the base?
Conversation
8444277
to
9acafd6
Compare
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.
Can you split the credentials role into a separate PR? I'm not sure if we want to merge the bucket role without the ability to list all objects in a bucket, but that shouldn't hold up the credentials work.
#5 has been created for gcp_setup_credentials role |
auth_kind: "{{ gcp_auth_kind }}" | ||
service_account_file: "{{ gcp_cred_file }}" | ||
project: "{{ gcp_project }}" |
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.
Why don't you use the role for creds setting here?
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 can also do that, I was just using it for collection role, but it should work too
We can leave this PR open in case things change, but we do not want to merge this as the limitations of the google.cloud collection prevent us from properly implementing this use case. |
Due to limitation with google.cloud collection, this role/playbook cannot delete source storage bucket as we can't list objects from one bucket (cannot delete non empty storage bucket), users also needs to provided list of objects to move.
#5 should be merged first for the CI to pass on this one