[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=60518#comment-60518 ] 

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

on the "immutability" topic -- would this have to be recursive?  my concern is where a plan refers to artifacts do we have to ensure we have immutable copies of each of those?  (which might be gigabytes if they are a lot of VM images...)

my thinking is that the `original_plan` here is a reference, which may have references, etc.  it is up to the users to have conventions around which of those references point at immutable content.  in prod you'd probably want them all to be immutable, but in dev you might weaken that (hence the SHOULD).

(alternatively we could easily take a copy of the depth=1 plan, and have MUST for that, but i'm not sure that's useful.)

BTW the way we solve this is with versions -- any version marked SNAPSHOT might have its content changed (so should be used sparingly, where you trust the authors of the other systems).  but anything else will be immutable.  (and anything which does not refer to a version gets resolved by the system and might use different versions depending when they are deployed.)  hardly earth-shattering but hopefully this helps.

(but i don't think we want to mandate a versioning scheme!)


> 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)