-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create 004-manifests.md #4
base: workloads
Are you sure you want to change the base?
Conversation
I think this proposal has the possibility to turn huge if we do it all at once. I recommend we use this as the basis for establishing that an aurie language will exist. I also recommend we create a specification document where part of the success criteria of some proposals is to update the specification. flowchart TD
proposal-->|updates|specification
specification-->|updates|implementation
implementation-->|feedback| proposal
implementation-->|feedback| specification
|
@cla-bot check |
Rechecking your CLA permissions. Remember to add your GitHub username to the .clabot file. You can run |
This manifest can be sourced from higher level applications, or even other aurae scripts. | ||
Application teams will be able to define their applications directly as valid aurae code. | ||
|
||
Notice how the application can be defined without connecting to an Aurae system, or accessing any of the subsystems at runtime. |
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.
how would that work under the hood? Is Aurae API expecting manifest like k8s would? Will there be "and now serialize it all to json and send" step in aurae DSL?
Have sense to reuse (part of) Open Application Model schema? theoretically vendor agnostic but close to k8s manifests style. |
No description provided.