-
Notifications
You must be signed in to change notification settings - Fork 767
Adjust variables for banner_etc_issue #14343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
The previously values with `'` would not work.
|
Skipping CI for Draft Pull Request. |
ATEX Test ResultsTest artifacts have been submitted to Testing Farm. Results: View Test Results This comment was automatically generated by the ATEX workflow. |
jan-cerny
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How have you reproduced the linked issue and how have you verified that this PR fixes the issue?
I can't reproduce the issue using Automatus. However, I can see it reproduced using contest, eg. in the daily productization run today.
I have run /per-rule/oscap/from-env contest test in a custom productization pipeline on this PR and the issue still persists.
What I find suspicious in the HTML report from the initial scan is that the test scenario banner_etc_issue_disa_dod_short.pass.sh doesn't seem to modify the /etc/issue file.
|
|
||
| elif remediation_type == "bash": | ||
| pattern = r'\(bash-populate\s*(\S+)\)' | ||
| pattern = r'\(bash-populate\s*([a-zA-Z0-9_]+)\)' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this change needed? It doesn't change the generated data stream. Both old and new version of the shared.sh is matched by the old expression.
Description:
Review each commit for details.
Rationale:
Fixes #13690
Review Hints:
Run automatus tests for