Skip to content

Integration [main]: implement redact to avoid leaking secrets from env [#186767925] IF the app is pushed with a manifest AND the app needs secrets set via environment variables THEN currently there is no way to avoid leaking secrets in the output of cf push commands. technically this could be avoided by not using a manifest and running: ``cf push --no-start cf set-env ... cf set-env ... cf set-env ... ... but that escalates quickly if the APP contains many secret things in it's env requirements.... #755

Integration [main]: implement redact to avoid leaking secrets from env [#186767925] IF the app is pushed with a manifest AND the app needs secrets set via environment variables THEN currently there is no way to avoid leaking secrets in the output of cf push commands. technically this could be avoided by not using a manifest and running: ``cf push --no-start cf set-env ... cf set-env ... cf set-env ... ... but that escalates quickly if the APP contains many secret things in it's env requirements....

Integration [main]: implement redact to avoid leaking secrets from env [#186767925] IF the app is pushed with a manifest AND the app needs secrets set via environment variables THEN currently there is no way to avoid leaking secrets in the output of cf push commands. technically this could be avoided by not using a manifest and running: ``cf push --no-start cf set-env ... cf set-env ... cf set-env ... ... but that escalates quickly if the APP contains many secret things in it's env requirements.... #755

Triggered via workflow run January 30, 2024 15:50
@nouseforanamenouseforaname
completed 453d358
Status Skipped
Total duration 4s
Artifacts

tests-integration.yml

on: workflow_run
EDGE CAPI and client creds  /  run-integration-tests
EDGE CAPI and client creds / run-integration-tests
Integration tests with EDGE CAPI  /  run-integration-tests
Integration tests with EDGE CAPI / run-integration-tests
MIN CAPI  /  run-integration-tests
MIN CAPI / run-integration-tests
Fit to window
Zoom out
Zoom in