[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (CAMP-175) Could remove "artifacts" or make them optional
[ https://issues.oasis-open.org/browse/CAMP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anish Karmarkar updated CAMP-175: --------------------------------- Affects Version/s: 1.2 > Could remove "artifacts" or make them optional > ---------------------------------------------- > > Key: CAMP-175 > URL: https://issues.oasis-open.org/browse/CAMP-175 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Improvement > Components: Spec > Affects Versions: 1.2 > Reporter: Alex Heneveld > Priority: Minor > > Some people we've talked to find the "artifacts" entry point for the plan confusing. Personally I like it and IMHO it *should* become the standard way to do things. > But right now people mostly seem to be building things up and so the "services" entry point is preferred -- look at how docker/fig/compose do it, and cloud foundry, and apache brooklyn. > To simplify we could remove all mention of "artifacts" or make them optional. > Or not ... this is just something to be aware of. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]