Skip to content
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

[master] Stop using egrep #66832

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[master] Stop using egrep #66832

wants to merge 1 commit into from

Conversation

Rudd-O
Copy link

@Rudd-O Rudd-O commented Aug 26, 2024

What does this PR do?

When egrep is used, a nasty warning from grep saying egrep should be replaced by grep -E appears on the executed command. This leads to failure matching returned values from semanage fcontext.

This fix fixes it.

What issues does this PR fix or reference?

Have not noticed any bugs reported on this.

Previous Behavior

Failure running selinux.fcontext_policy_present.

New Behavior

It works.

Merge requirements satisfied?

[NOTICE] Bug fixes or features added to Salt require tests.

Commits signed with GPG?

No

Please review Salt's Contributing Guide for best practices, including the
PR Guidelines.

See GitHub's page on GPG signing for more information about signing commits with GPG.

When egrep is used, a nasty warning from grep saying egrep should be replaced by grep -E appears on the executed command.  This leads to failure matching returned values from `semanage fcontext`.

This fix fixes it.
@Rudd-O Rudd-O requested a review from a team as a code owner August 26, 2024 09:35
@salt-project-bot-prod-environment salt-project-bot-prod-environment bot changed the title Stop using egrep [master] Stop using egrep Aug 26, 2024
@dmurphy18
Copy link
Contributor

dmurphy18 commented Aug 26, 2024

@Rudd-O This PR requires a changelog entry and tests new or updated if current tests are insufficient to test the code changes, no PR is accepted without the above.

You might want these changes to appear on the 3006.x or 3007.x branch for an earlier release, given the master branch will become 3008 some time in the future.

Copy link
Contributor

@twangboy twangboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please provide a changelog and a test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants