Spotted some outdated procedures for managing RBAC for Hub. Needs to reflect 1.2 UI changes.

Several storage and RAM requirements reference units of Gb which is gigabits, however these measurements are clearly meant to be in gigabytes (GB).

Additionally, some usages of GB are not separated by a space as required per the style guide: https://redhat-documentation.github.io/supplementary-style-guide/#gb

Just a running list of ansible-navigator code PRs that have changes or added some minor things (to remind me to add them to the docs):

• note pull-policy options for loading EE
• note -ll debug for logging levels on troubleshooting
• add info from upstream FAQ
• add 'how to use navigator TUI' to explain the bits and bobs of how the UI works.
• ansible/ansible-navigator#399 - add support for {{ }} in the navigator command syntax
• ansible/ansible-navigator#379 - adds no-color support for accessibility
• ansible/ansible-navigator#369 - creates support for ansible-navigator --version.
• ansible/ansible-navigator#340 - changes to :run: and artifact creation
• ansible/ansible-navigator#339 - changes to settings file
• ansible/ansible-navigator#332 - renames ee-details
• ansible/ansible-navigator#331 - changes images subcommand
• ansible/ansible-navigator#317 - added pull policy
• ansible/ansible-navigator#316 - added --help-inventory
• ansible/ansible-navigator#315 - added --version
• ansible/ansible-navigator#312 - fixes prev/next 'buttons'
• ansible/ansible-navigator#308 - might have updated the welcome TUI screen?
• ansible/ansible-navigator#301 - may not need doc changes if we don't have any help 'screen' output.
• ansible/ansible-navigator#280 - details on logging
• ansible/ansible-navigator#225 - help-doc subcommand added

Diagrams are requested to cover the various installation scenarios covered by the platform installer.

Additional updates may be required on the Tower docs side to include Hub 3.8 and higher.

The builder guide has references to several links to other downstream content, some of which are in progress:

• section 2.4.2: "how to download a collection from hub"
• section 3.2: "For more information, please reference the Pulling from Protected Registries section of the Execution Environment documentation."

With Summit on 04/26, AAP will update to show an updated sidebar navigation. Update the procedures we have to reflect these UI changes. See the new nav bar layout on https://cloud.redhat.com/beta/

Check off the titles that looks good or needs updating:

Catalog:

• Tech Preview - Pass
• Catalog Getting Started - Pass
• ITSM - Pass

Hub:

• Ansible Galaxy collections - Pass
• Hub User Access - Pass
• Namespaces - Pass
• Publish proprietary content - Pass
• Hub Getting Started - Pass
• Uploading collections - Pass

Insights:

• Job explorer - Fail. Needs fixes
• Automation calculator - Pass

AA 1.1 release notes need to be assembled for the next update.

Because AAP on Cloud is moving to a new splash page and the title artifacts (master.adoc and docinfo.xml) are sourced downstream in GitLab we need to create upstream titles for that content.

Update the titles to add the inclusive language statement from aap-common.

AAP documentation requires a section that describes automation analytics. The below texts should provide an example of what's needed:

What is Automation Analytics
Automation Analytics is a feature of the Red Hat Ansible Automation Platform. It is a cloud-based service that uses information from your automation and automation infrastructure. Automation Analytics brings knowledge and insights in order to demonstrate automation value, find both automation success and automation opportunities, and proactively discover problems in automation workloads across the enterprise.

Additional information to include:

• Who is it for (audience)
• How to access Automation Analytics
• How to populate
• What it does
• Clusters
• Notifications
• Organization screen

With the recent naming changes to certain AAP services (Tower > Controller, Analytics > Insights), we'll need to update our docs to reflect the new names.

Titles that need updating:

• analytics/job-explorer
• analytics/user-access
• catalog/tech-preview

The ports and protocols table for the database server shows that pg_port is the variable used to configure the SSH connection. It should be ansible_port.

.PostgreSQL
[options="header"]
|===
|Port |Protocol |Service |Direction |Installer Inventory Variable |Required for
|22
|TCP
|SSH
|Inbound and Outbound
|`pg_port`        <--- this is the issue
|Remote access during installation
|5432
|TCP
|Postgres
|Inbound and Outbound
|`pg_port`
a|Default port

Externalize the bash sections of each Jenkins job to synchronize the content of this repository downstream.

When installing Ansible Core and Hub in a 2 server all imcompassing install you need to ensure that you open the port that you are using to talk to the Postgres DB on the Ansible Core server in order for the Automation Hub server to reach and install the needed DB information in the all in one install.

For example the Getting Started guide contains the filename as the link which is hard to read.

https://github.com/ManageIQ/catalog_docs/blob/master/doc/assembly_Getting_started.adoc

The attributes file needs to be updated with the WIP platform & component names. Working file for component and feature names is here.

create new branch from master titled main. Lock master.

Inform team when this action will happen and supply directions for updating.