-
Notifications
You must be signed in to change notification settings - Fork 9
Naming Guidelines
Tim Etchells edited this page Sep 13, 2021
·
4 revisions
All the secret names should follow CONSTANT_CASE convention.
Below are the names of the secrets that we currently use in our workflows:
- REGISTRY_USER: Username for the image registry.
- REGISTRY_PASSWORD: Password or token for the image registry.
- OPENSHIFT_SERVER: Openshift API Server URL.
- OPENSHIFT_TOKEN: Openshift Bearer Token.
- OPENSHIFT_USER: Openshift username.
- OPENSHIFT_PASSWORD: Openshift Password.
When naming Inputs and Outputs, use snake_case.
Some actions were written with kebab-case, so they remain that way. Actions must be internally consistent with their naming.
Similarly, when writing workflows, try to use snake case for job and step IDs.