[OASIS Issue Tracker] (CAMP-184) Entity Immutability

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60517#comment-60517 ] 

Alex Heneveld commented on CAMP-184:
------------------------------------

two comments:

* can we call this `original_plan` ?  because there might also have a `current_plan`.

* and can req 2 (immutable) be changed to a SHOULD ?  it's a bad idea to change willy-nilly but there may be times when someone might want to or be able to.  a MUST is burdensome, particularly where there are transitive dependencies, and i'm not sure there are interoperability benefits.

i also wonder whether this needs to be part of the spec at all.  audit support requires more:  if an assembly is changed for instance, that would have to be recorded (e.g. the "action log" in Solum, as Adrian advises).  it is useful to have this for informational purposes to prevent confusion, for which a SHOULD seems appropriate.

> Entity Immutability
> -------------------
>
>                 Key: CAMP-184
>                 URL: https://issues.oasis-open.org/browse/CAMP-184
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Assignee: Gilbert Pilz
>            Priority: Minor
>
> For audit purposes we would like to ensure the Plan from which an Assembly is initiated is immutable.  In general it may be best to ensure that all entities within the domain model are "copy-on-write", and we can have a generic way of accessing versions of entities through the API.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)