-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Remove duplicate / unnecessary setting of fields in post_create code #22214
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
Labels
mmv1-generator
Provider-wide changes to resource templates or other generator changes
size/xl
technical-debt
Milestone
Comments
melinath
added a commit
to melinath/magic-modules
that referenced
this issue
Apr 2, 2025
This is now handled by the changes in hashicorp/terraform-provider-google#22214
This was referenced Apr 2, 2025
Merged
This was referenced Apr 3, 2025
This was referenced Apr 3, 2025
This was referenced Apr 4, 2025
This was referenced Apr 11, 2025
Open
Merged
This was referenced Apr 15, 2025
Removed monitoring group set_computed_name post_create
hashicorp/terraform-provider-google-beta#9791
Merged
This was referenced Apr 15, 2025
This was referenced Apr 16, 2025
Merged
This was referenced Apr 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
mmv1-generator
Provider-wide changes to resource templates or other generator changes
size/xl
technical-debt
What kind of contribution is this issue about?
Other (specify in details)
Details
GoogleCloudPlatform/magic-modules#12939 fixed an issue with resource generation where resources had to set fields in post_create custom code if they were needed for the follow-up Read request. This ticket covers follow-on work to evaluate usage of
d.Set
in post_create code and remove now-redundant usage.We should also remove all usage of set_computed_name.tmpl if possible. This is used in a bunch of places:
Other:
References
No response
The text was updated successfully, but these errors were encountered: