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

packer: share AMIs with the entire aws scylla organization #518

Merged
merged 1 commit into from
Apr 7, 2024

Conversation

benipeled
Copy link
Contributor

With this change, AMIs wil be shared with the entire aws scylla org (instead of specific accounts) to allow all accounts to use the AMI before it is promoted + avoid the need to maintain a list of accounts that require AMI access,

This is about the AMI, on another change on pkg we need to adjust the change_snapshot_permissions() function to loop through all the org account

Ref https://github.com/scylladb/scylla-pkg/issues/3529

In order to allow all accounts to use the AMI before it is
promoted + avoid the need to maintain a list of accounts require AMI
access
@benipeled
Copy link
Contributor Author

@yaronkaikov
Copy link
Collaborator

AFAIK the cloud needs those images on the enterprise branch for testing, I don't see a reason to backport this.

@benipeled
Copy link
Contributor Author

AFAIK the cloud needs those images on the enterprise branch for testing, I don't see a reason to backport this.

Yes, and they probably need it for future releases only but since it's a minor trivial change we'll backport it

@yaronkaikov
Copy link
Collaborator

AFAIK the cloud needs those images on the enterprise branch for testing, I don't see a reason to backport this.

Yes, and they probably need it for future releases only but since it's a minor trivial change we'll backport it

We should backport if it's needed or if it's improved something (even if it's a minor and there is no risk). Let's verify before if it's needed for releases. Thanks

@benipeled
Copy link
Contributor Author

AFAIK the cloud needs those images on the enterprise branch for testing, I don't see a reason to backport this.

Yes, and they probably need it for future releases only but since it's a minor trivial change we'll backport it

We should backport if it's needed or if it's improved something (even if it's a minor and there is no risk). Let's verify before if it's needed for releases. Thanks

Yes it's an improvement and I'm not sure what verification you're looking for here,
In any case, let's please avoid a long discussion about something so minor that at the end will effect/help nothing

@yaronkaikov
Copy link
Collaborator

AFAIK the cloud needs those images on the enterprise branch for testing, I don't see a reason to backport this.

Yes, and they probably need it for future releases only but since it's a minor trivial change we'll backport it

We should backport if it's needed or if it's improved something (even if it's a minor and there is no risk). Let's verify before if it's needed for releases. Thanks

Yes it's an improvement and I'm not sure what verification you're looking for here, In any case, let's please avoid a long discussion about something so minor that at the end will effect/help nothing

My point exactly to will help nothing :-)

@benipeled benipeled merged commit f6400ec into scylladb:next Apr 7, 2024
1 check passed
@benipeled benipeled deleted the share_with_org branch April 7, 2024 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants