-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: AIP-128 – Declarative-friendly interfaces #32
base: main
Are you sure you want to change the base?
Conversation
going into reconciliation was user or system action. | ||
|
||
**Note:** Services responding to a `GET` request **must** return the resource's | ||
current state (not the intended state). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
subject to preconditions (e.g. etags) presumably
landscape, and tooling is responsible for making whatever changes are necessary | ||
to achieve the user's specification. | ||
|
||
These tools are **declarative**: rather than specifying specific _actions_ to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missing something here.... are you suggesting these types of declarations will precipitate standard operations (e.g. POST/PUT/GET/DELETE/PATCH?) Or are you suggesting something more like JMX with an introspection capability? Or something totally different and I'm just not getting it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. 👍
I made the oas example a bit more explicit.
No description provided.