Use cf local with the app's manifest.yml

[ngscchung]

I found that cf local run or stage will not recognize my manifest.yml. I have to re-input those info like app names or host through command line or create a separate local.yml ... is it possible to make cf local recognize the app's original manifest.yml?

[sclevine]

Ignoring manifest.yml is an intentional design decision that I don't currently have plans to change.

Reasons include:

• Local app configuration and remote app configuration are often different. The service credentials, environment secrets, and app domain are generally going to be different for locally-running apps.
• The manifest.yml format is missing many configuration options that CF Local needs or will need, such as full service binding credentials, staging/running environment variable groups, and droplet file paths.
• It would be confusing to modify manifest.yml on cf local pull, and doing so could result in adding secrets to manifest.yml that should not be checked into VCS.

I might consider adding an option to local.yml to use the environment variables from an app specified in manifest.yml. Is this a compelling option for your use case?

[ngscchung]

Our use case is to setup our deployment pipeline to trigger cf local and construct an unittest environment that is (almost) identical to the actual CF runtime environment and run the unittest before cf push.

Understand your design idea and your suggested enhancement will help. Originally I'm just thinking if cf local would follow the original manifest.yml by default, and override/supplement any additional options specified in local.yml that are specific for cf local usage, but it's okay if you want to prevent any potential confusions.