Skip to content
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.

Sign up for GitHub

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

component should be mutable in alpha2 #343

Merged
merged 1 commit into from
May 19, 2020
+1 −1
Merged

component should be mutable in alpha2 #343

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 7.application_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ In addition, as an application configuration is released, its _component instanc

To accommodate this definition of a release, an OAM platform SHOULD make the following assumptions:

- A component (as defined in the [component model](4.component.md) section) is immutable. It should not be changed after creation.
- A component (as defined in the [component model](4.component.md) section) is mutable. Upgrade can happen by updating the component, e.g. updating image.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should merge this paragraph with the paragraph below, because change on a Component will results a new release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. Will do it.

- Any change to an [application configuration](4.application_configuration.md) results (conceptually) in a new release that supersedes older releases.
* If an application configuration is updated, and the new version includes components not present in the original application configuration, component instances MUST be created
* If an application configuration is updated, and the new version does not have a record of a component that the previous application configuration contained, that component instance MUST be deleted
Expand Down