-
Task
-
Resolution: Done
-
Normal
-
None
-
False
-
None
-
False
-
-
-
None
1. - [x] Mandatory: Add the required version to the Fix version/s field.
2. - [x] Mandatory: Choose the type of documentation change or review.
- [x] We need to update to an existing topic
- [ ] We need to add a new document to an existing section
- [ ] We need a whole new section; this is a function not
documented before and doesn't belong in any current section
- [ ] We need an Operator Advisory review and approval
- [ ] We need a z-Stream (Errata) Advisory and Release note
for MCE and/or ACM
3. - [x] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:
4. - [x] Mandatory for GA content:
- [x] Add steps, the diff, known issue, and/or other important
conceptual information in the following space:
- [ ] *Add Required access level *(example, *Cluster
Administrator*) for the user to complete the task:
- [ ] Add verification at the end of the task, how does the user
verify success (a command to run or a result to see?)
- [ ] Add link to dev story here:
5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.
I just noticed this:
In the linked doc is the sentence:
To view the security guide, see Risk and compliance.
A couple of comments on that sentence:
- We don't call the Governance book the "security guide" in general do we? It seems like the link should say either Security Overview or Governance.
- "Risk and compliance" is not what we call any doc in ACM anymore is it? We have been shifting to focus more on Governance and Policy and allowing ACS to own Risk and Compliance.