feat(cloudFoundryDeploy): add cfTrace param to customize cf log output #5300
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
niki4
changed the title
ashlymat
reviewed
Mar 21, 2025
|
/it-go |
added 3 commits
March 21, 2025 15:34
|
|
Since we sorted the issue with See INC11326947 for details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new param "cfTrace" for cloudFoundryDeploy step. Prior to this PR the value we used for CF CLI log output was hardcoded to "cf.log" whilst some users wanted to do not create that log file at all or just print it to the stdout instead.
cfTrace set related env var CF_TRACE used by CF CLI.
This change backward compatible with existing Piper pipeline configurations, no changes need.
Checklist