-
Notifications
You must be signed in to change notification settings - Fork 625
[AIP-163] Approve the change validation AIP. #437
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
Conversation
transferring from issue-573078166: It would be great to expand the guidance in AIP-163 on how to handle standard methods and general resource lifecycle. For example, what is the expected behavior of a Create or Delete with
A couple places where an amendment for dry run could help:
|
Happy to add something for this. Incidentally. the answers to these questions are:
Yes.
Yes (and anything else would not make sense).
No. The dry run succeeded. |
This seems overly strong: a validate_only call typically would not create state in a database, but certain classes of errors can only happen when a call to commit a transaction is actually made. |
This is a great point, thanks @jasonmc. I have amended the language to: "a request using |
I did a minor re-word to try and be more clear about this; let me know if you think it is clear enough. |
This issue is intended for public comment, and should remain open through March 27, 2020.