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

Adding the namespace_labels field to the GKE Hub Scope resource #1992

Conversation

modular-magician
Copy link
Collaborator

This PR is a follow-up to PR #8882. In addition to labels, the GKE Hub Scope resource has a namespace_labels field.

Release Note Template for Downstream PRs (will be copied)

gkehub2: added `namespace_labels` field to `google_gke_hub_scope` resource

Derived from GoogleCloudPlatform/magic-modules#9972

* initial commit for scope-level namespace labels

* Add validation exceptions for the  field of the GKEHub Scope and Namespace resources to be of type

* Undoing unnecessary changes

* Fixing the type of Scope namespace_labels field

[upstream:3e13564ac5d3ac814949b399e0fd56058445a717]

Signed-off-by: Modular Magician <[email protected]>
@modular-magician modular-magician requested a review from a team as a code owner February 26, 2024 21:52
@modular-magician modular-magician requested review from melinath and removed request for a team February 26, 2024 21:52
@modular-magician modular-magician merged commit 8f5a507 into GoogleCloudPlatform:main Feb 26, 2024
3 checks passed
Copy link

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

@modular-magician modular-magician deleted the downstream-pr-3e13564ac5d3ac814949b399e0fd56058445a717 branch November 18, 2024 04:06
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.

1 participant