Skip to content

Conversation

@neilmb
Copy link

@neilmb neilmb commented Nov 21, 2023

Changes proposed in this pull request:

  • Change README a tiny bit to clarify the role of the cf_manifest and the cf_vars_file variables

- `cf_manifest:` to use a different manifest file (instead of the default `manifest.yml`)
- `cf_vars_file:` to [specify values for variables in the manifest file](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#variable-substitution)
- `cf_command:` to specify a CF sub-command to run (instead of the default `push -f $MANIFEST -vars-file $VARS_FILE --strategy rolling`)
- `cf_command:` to specify a CF sub-command to run (instead of the default `push -f $cf_manifest -vars-file $cf_vars_file --strategy rolling`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `cf_command:` to specify a CF sub-command to run (instead of the default `push -f $cf_manifest -vars-file $cf_vars_file --strategy rolling`)
- `cf_command:` to specify a CF sub-command to run (instead of the default `push -f $MANIFEST --strategy rolling`)

So the default command does not include a vars file: https://github.com/cloud-gov/cg-cli-tools/blob/main/entrypoint.sh#L38

And $MANIFEST is the variable that is used, which will respect the value of cf_manifest if set, otherwise it will default to manifest.yml:

https://github.com/cloud-gov/cg-cli-tools/blob/main/entrypoint.sh#L30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants