fortify update to 1.1.2320154-bb.14
Package Merge Request
Package Changes
https://repo1.dso.mil/big-bang/product/packages/fortify/-/blob/1.1.2320154-bb.14/CHANGELOG.md
Package MR
big-bang/product/packages/fortify!157 (merged)
For Issue
Closes (link to issue here)
Upgrade Notices
The .Values.ssc.config.log4j
section has been streamlined — previous values will not work. See CHANGELOG
or values.yaml
for more on the current log customization options.
Merge request reports
Activity
- A deleted user
added botmr fortify statusreview labels
assigned to @dpritchettrm
requested review from @chris.oconnell, @michaelmartin, and @andrewshoell
note for potential anchors looking to test this — the two new config options are:
- quick and dirty debug logging:
addons.fortify.values.ssc.config.log4j.enableDebugConfig=true
- fully override the fortify log4j config with your own 300-line xml string:
addons.fortify.values.ssc.config.log4j.customXMLConfigString
-
setting this will override the aboveenableDebugConfig
option -
For your testing convencience I'm attaching the same repo-localtests/test-values.yaml
I used. This one should prependCUSTOM LOGS HERE
to log output so it'll be easy to see in STDOUT that it was successfully applied: test-values.yaml-
Note that you'll need to nest theconfig.log4j
options from the above attachment underaddons.fortify.values
.
-
-
Edited by Daniel Pritchett- quick and dirty debug logging:
changed milestone to %2.30.0
mentioned in commit c16b72aa