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

AAP-26663-edits updated section 2.3.3 #1626

Open
wants to merge 1 commit into
base: aap-hardening-2.5
Choose a base branch
from

Conversation

emurtoug
Copy link
Contributor

AAP-26663

Edited the following module for Chapter 2.3.3 of Red Hat Ansible Automation Platform Hardening Guide v2.5: Applying defensive security controls

Updated file:

modules/aap-hardening/ref-apply-defensive-security-controls.adoc

@emurtoug emurtoug added Ready for review This PR needs review and approval by members of the docs team Ready for technical review Content is ready for technical reviews 2.5 Content applies to AAP 2.5 labels Jul 24, 2024
Copy link
Contributor Author

@emurtoug emurtoug left a comment

Choose a reason for hiding this comment

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

Line 11:
jamesmarshall24 last week
for "controllers, hubs, and EDA controllers" I would recommend checking with branding to get the name/shortname of each of these and probably parameterize them similar to PlatformName/PlatformNameShort. Maybe something to do in another PR?

Comment copied from PR 812: https://github.com/ansible/aap-docs/pull/812/files#r1682936810

Copy link
Contributor Author

@emurtoug emurtoug left a comment

Choose a reason for hiding this comment

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

Lines 42-49:
jce-redhat 2 days ago
did this procedure go through technical QA? it worked on a test system i built, but formal QA would be better.

Comment copied from PR 812: https://github.com/ansible/aap-docs/pull/812/files#r1686910466

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.5 Content applies to AAP 2.5 Ready for review This PR needs review and approval by members of the docs team Ready for technical review Content is ready for technical reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant