{"action":"created","issue":{"url":"https://api.github.com/repos/appc/spec/issues/108","labels_url":"https://api.github.com/repos/appc/spec/issues/108/labels{/name}","comments_url":"https://api.github.com/repos/appc/spec/issues/108/comments","events_url":"https://api.github.com/repos/appc/spec/issues/108/events","html_url":"https://github.com/appc/spec/issues/108","id":54134160,"number":108,"title":"spec: dependencies details > manifest merge strategy","user":{"login":"frntn","id":437946,"avatar_url":"https://avatars.githubusercontent.com/u/437946?v=3","gravatar_id":"","url":"https://api.github.com/users/frntn","html_url":"https://github.com/frntn","followers_url":"https://api.github.com/users/frntn/followers","following_url":"https://api.github.com/users/frntn/following{/other_user}","gists_url":"https://api.github.com/users/frntn/gists{/gist_id}","starred_url":"https://api.github.com/users/frntn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/frntn/subscriptions","organizations_url":"https://api.github.com/users/frntn/orgs","repos_url":"https://api.github.com/users/frntn/repos","events_url":"https://api.github.com/users/frntn/events{/privacy}","received_events_url":"https://api.github.com/users/frntn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-13T00:30:12Z","updated_at":"2015-01-13T08:05:23Z","closed_at":null,"body":"While the spec specifies how acis are being extracted on one another (as long as ̀`pathWhitelist` allows it), it does not gives informations about the manifest.\r\n\r\nAs first proposal what about these \"merge strategy\" options :\r\n- **`none`** : keep original manifest unmodified,\r\n- **`array`** : assembles a value from every matching level of the hierarchy,\r\n- **`hash`** : recursively merge hash keys.\r\n\r\nThe behaviour description *must* be shipped inside the image but (and that's the part I don't like!!) the option it self should never be overwritten.\r\n\r\n*(I think we loose here the simplicity we want for the spec, but the problem do exists so I'm just hoping this proposal will help as a starting point for a better answer)* "},"comment":{"url":"https://api.github.com/repos/appc/spec/issues/comments/69708532","html_url":"https://github.com/appc/spec/issues/108#issuecomment-69708532","issue_url":"https://api.github.com/repos/appc/spec/issues/108","id":69708532,"user":{"login":"jonboulle","id":2601015,"avatar_url":"https://avatars.githubusercontent.com/u/2601015?v=3","gravatar_id":"","url":"https://api.github.com/users/jonboulle","html_url":"https://github.com/jonboulle","followers_url":"https://api.github.com/users/jonboulle/followers","following_url":"https://api.github.com/users/jonboulle/following{/other_user}","gists_url":"https://api.github.com/users/jonboulle/gists{/gist_id}","starred_url":"https://api.github.com/users/jonboulle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jonboulle/subscriptions","organizations_url":"https://api.github.com/users/jonboulle/orgs","repos_url":"https://api.github.com/users/jonboulle/repos","events_url":"https://api.github.com/users/jonboulle/events{/privacy}","received_events_url":"https://api.github.com/users/jonboulle/received_events","type":"User","site_admin":false},"created_at":"2015-01-13T08:05:23Z","updated_at":"2015-01-13T08:05:23Z","body":"@frntn Actually there is no concept of manifest merging. dependencies/`pathWhitelist` _only_ talks about constituent files of an ACI.\r\n\r\n> The behaviour description must be shipped inside the image but (and that's the part I don't like!!) the option it self should never be overwritten.\r\n\r\nI don't really understand what you mean here - what specifically don't you like, and what would you rather see?\r\n\r\nAlso, to be clear, most options _can_ be overridden in the CRM/at runtime (the exact semantics we are still trying to thrash out in #83/#84). \r\n"}}