-
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
describe component/trait version in AppConfig #237
Comments
Agreed, we do need a way to allow application operators to specify the version of a component, trait, and scope to use. The assumption here is that a runtime can have multiple versions of a component schematic, trait definition, and scope definition registered. We can state this explicitly in the spec by saying that a fully-qualified unique identifier for a component schematic, trait definition, and scope definition is:
For example, the fully-qualified name for this component schematic: apiVersion: core.oam.dev/v1alpha1
kind: ComponentSchematic
metadata:
name: frontend
annotations:
version: v1.0.0
description: >
Sample component schematic that describes the administrative interface for our Twitter bot.
spec:
... would be The runtime would need to track this. It might require some additional munging of the OAM spec files to get it to work in each runtime. In the Application Config, |
Yeah, I totally agree add a |
Now we have versions in annotation both
Trait
andComponent
, but we didn't define them in AppConfig, so we don't know which version of Trait/Component was used in AppConfig.Have version explicitly defined in AppConfig has two benifits:
The text was updated successfully, but these errors were encountered: