-
Notifications
You must be signed in to change notification settings - Fork 251
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
Where will the Application Metadata be defined #87
Comments
Do we need this? Or can we just add a few labels to the OperationalConfiguration and get the same thing? |
We already have the perfect construct in the spec for exactly this scenario: scopes! An "application metadata" scope can easily be defined to handle this, except maybe the dependencies, but I'm not sure what that dependency tracking would do anyway. Nonetheless, I think an application metadata scope might even be a candidate for a core scope, if we feel strongly enough about it. |
Is someone working on defining an Application Metadata scope? Currently, only Network and Health scopes are defined. |
I will take a stab as defining this, but I have a few questions: @wonderflow - can you help me understand the 'dependencies' and 'components' part of your example? |
@hongchaodeng will give a PR, then we can discuss from that |
Now we have Configuration to combine multiple components together which define an Application instance, but if we want to define multiple applications and there will be some dependency on these applications. So we may need a place (or a concept) to define Application Metadata.
Application Metadata is used to store application level information, such as application logo, providers, maintainers, dependencies, etc. We will be able to launch a set of applications if we have defined the application metadata.
For example, we define this Application Meta
With ApplicationMeta we will be able to define application relationships.
The text was updated successfully, but these errors were encountered: