using the existing app configuration

[afeld]

using the existing app configuration

[concourse-bot]

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #103345328 using the existing app configuration

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

[adelevie]

@afeld what does it mean for a manifest to be "complete"? How can I verify this on my own manifests?

[afeld]

@adelevie I mean that deploying with the same codebase+manifest to a new application (in the Cloud Foundry sense) will yield the same results. For example, if an API secret is set as a user-provided environment variable (rather than, say, a user-provided service instance and bound within the manifest), deploying to a new application would not have access to that secret. In other words, the principle of least surprise would suggest that deploying an application with Autopilot to yield the same results as deploying with cf push, regardless of what is stated in the manifest vs. previously set through the command line.

Not sure that I'm explaining it well...?

[afeld]

I have come around in deciding that, while this might be convenient for switching to autopilot, it's actually an antipattern.