Skip to content

resourceIdentity/MMv1: skip id values that aren't present in resource schema#12233

Merged
modular-magician merged 1 commit into
hashicorp:mainfrom
modular-magician:downstream-pr-1de371e2255e87b24bdcd4040e223ec54f7e7cdc
May 14, 2026
Merged

resourceIdentity/MMv1: skip id values that aren't present in resource schema#12233
modular-magician merged 1 commit into
hashicorp:mainfrom
modular-magician:downstream-pr-1de371e2255e87b24bdcd4040e223ec54f7e7cdc

Conversation

@modular-magician
Copy link
Copy Markdown
Collaborator

When looking into list mmv1 i noticed a bug where an import_format can be used despite the values not being present in the resource's schema.

This adds a check to prevent schema field from being included in identity schema. An example of this is alloydb_user not including project in the resource schema:
https://github.com/GoogleCloudPlatform/magic-modules/blob/59d0a15a26f0edd5272999c5d2efe209cffea033/mmv1/products/alloydb/User.yaml#L22-L28

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.


Derived from GoogleCloudPlatform/magic-modules#17532

…ce schema (#17532)

[upstream:1de371e2255e87b24bdcd4040e223ec54f7e7cdc]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 8d29e01 into hashicorp:main May 14, 2026
3 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.

1 participant