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

feat: add support for assigning admin role in Artifact Registry #52

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

lmanowski-esky
Copy link

@lmanowski-esky lmanowski-esky commented Jan 14, 2025

The capability to assign the repo administrator role (roles/artifactregistry.adminRepo) in Artifact Registry to specific service accounts or users has been introduced. This enhancement allows authorized individuals to delete images from Artifact Registry repositories, which is essential for scenarios requiring artifact management by designated accounts.

@lmanowski-esky lmanowski-esky requested review from prabhu34 and a team as code owners January 14, 2025 09:00
Copy link

google-cla bot commented Jan 14, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@lmanowski-esky lmanowski-esky changed the title add support for assigning admin role in Artifact Registry feat: add support for assigning admin role in Artifact Registry Jan 14, 2025
@lmanowski-esky
Copy link
Author

@prabhu34

@prabhu34
Copy link
Collaborator

lmanowski-esky

Thanks for the PR. Should we bake this in this module or can this requirement be handled outside?

@apeabody Happy to hear your thoughts.

@lmanowski-esky
Copy link
Author

lmanowski-esky

Thanks for the PR. Should we bake this in this module or can this requirement be handled outside?

@apeabody Happy to hear your thoughts.

This should be added to ensure consistency.

@@ -178,12 +178,12 @@ variable "vpcsc_policy" {
// IAM
variable "members" {
type = map(list(string))
description = "Artifact Registry Reader and Writer roles for Users/SAs. Key names must be readers and/or writers"
description = "Artifact Registry Reader, Writer and Admin roles for Users/SAs. Key names must be readers and/or writers and/or admins"
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Oxford comma

Suggested change
description = "Artifact Registry Reader, Writer and Admin roles for Users/SAs. Key names must be readers and/or writers and/or admins"
description = "Artifact Registry Reader, Writer, and Admin roles for Users/SAs. Key names must be readers, writers, and/or admins"

depends_on = [
google_artifact_registry_repository.repo
]
}
Copy link
Contributor

@apeabody apeabody Jan 22, 2025

Choose a reason for hiding this comment

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

For LINT (also run 'make docker_generate_docs' prior to commit)

Suggested change
}
}

])
error_message = "The supported keys are readers and writers."
error_message = "The supported keys are readers, writers and admins."
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
error_message = "The supported keys are readers, writers and admins."
error_message = "The supported keys are readers, writers, and admins."

@apeabody
Copy link
Contributor

lmanowski-esky

Thanks for the PR. Should we bake this in this module or can this requirement be handled outside?
@apeabody Happy to hear your thoughts.

This should be added to ensure consistency.

Agreed - As this is an minor additional resource, and we already include Reader, and Writer, I think it makes sense to add the base module.

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