Skip to content

Latest commit

 

History

History
41 lines (29 loc) · 1.53 KB

prow-adding-secrets.md

File metadata and controls

41 lines (29 loc) · 1.53 KB
Raw

Adding secrets to Prow

Updating an existing secrets values

integr8tly-ci-secrets values

Create a new env file (integr8ly-ci-secrets.env) with all env vars listed below:

HEIMDALL_REGISTRY_PASSWORD=
HEIMDALL_REGISTRY_USERNAME=
INTLY_OPERATOR_COVERALLS_TOKEN=
ocm-refresh-token=

integr8ly-tower-secrets values

Create a new env file (integr8ly-tower-secrets.env) with all env vars listed below:

OPENSHIFT_MASTER=
TOWER_OPENSHIFT_USERNAME=
TOWER_OPENSHIFT_PASSWORD=
TOWER_LICENSE=
TOWER_USERNAME=
TOWER_PASSWORD=

Create the secret

oc create secret generic <secret-name> --from-env-file=./<file-name> --dry-run -o yaml | oc replace -f -

An example of the changes required to make this secret available in the test container can be found here.

An example of how to access the contents of the secret in your test scripts can be found here.

Note:

Injecting secrets into the test container this way only works when using container tests This approach of injecting extra secrets into the test container is not supported by template tests used for e2e testing.