You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AIP-163 gives guidelines for how APIs can provide a mechanism to validate requests. Most APIs do not implement this AIP. For APIs that do implement it (or something similar), I believe we could add support for calling it during the plan computation process (since it looks like we have access to configured clients from CustomizeDiff).
At a minimum, it would be good to choose three resources that support validate_only and implement & document something that works for all of them. It could be a flag in MMv1, or it could be a shared helper function - maybe even a CustomizeDiff function if there were a way to make a generic one that just gets plugged in.
melinath
changed the title
Generated support for API-side validation via validate_only param or similar
Generic support for API-side validation via validate_only param or similar
Dec 17, 2024
What kind of contribution is this issue about?
MMv1-based resource
Details
AIP-163 gives guidelines for how APIs can provide a mechanism to validate requests. Most APIs do not implement this AIP. For APIs that do implement it (or something similar), I believe we could add support for calling it during the plan computation process (since it looks like we have access to configured clients from CustomizeDiff).
At a minimum, it would be good to choose three resources that support validate_only and implement & document something that works for all of them. It could be a flag in MMv1, or it could be a shared helper function - maybe even a CustomizeDiff function if there were a way to make a generic one that just gets plugged in.
References
#20641
The text was updated successfully, but these errors were encountered: