[RFC0034] App Manifests v2

[beyhan]

This is a tracking issue for the implementation of https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0034-v2-app-manifests.md

Tasks

Preview Give feedback

1. ...

[norman-abramovitz]

There was convention that got lost over time. The use of underscores was for names given that what is most programming languages used. Dashes was used to separate combined keys like combining GUIDS. The colon was to separate major components like it does in the /etc/passwd file. If you are considering moving towards only underscores, you should consider a convention that covers all known usages and provide some form of escaping or mapping functions when an outside process needs a format.

If you want additional information, you can contact me through slack or github.

[norman-abramovitz]

When breaking out components like services into their own top level item, please do not lose the knowledge how those components relate back to the other other components. A person should be able see or draw a graph of the relationships. What I saw in the example cases the relationships are lost.

If you want additional information, you can contact me through slack or github.

[norman-abramovitz]

I hope we do not rename the manifest or have a better name than "space manifest." I feel it needs to make sense to the role that the api/cli interface is was designed for. Unless you are planning to put all pushed processes into a single space manifest, the use of the term "space manifest" would be very confusing. It is possible to design an interface where it makes sense but that might be V4 interface.

If you want additional information, you can contact me through slack or github.