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....
#756
Triggered via workflow run
January 30, 2024 21:14
nouseforaname
completed
453d358
Status
Success
Total duration
1h 35m 34s
Artifacts
–
tests-integration.yml
on: workflow_run
Integration tests with EDGE CAPI
/
run-integration-tests
47m 32s
EDGE CAPI and client creds
/
run-integration-tests
47m 21s
MIN CAPI
/
run-integration-tests
1h 35m
Annotations
3 warnings
EDGE CAPI and client creds / run-integration-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: LouisBrunner/checks-action@v1.6.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Integration tests with EDGE CAPI / run-integration-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: LouisBrunner/checks-action@v1.6.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
MIN CAPI / run-integration-tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: LouisBrunner/checks-action@v1.6.2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|