Link fixes in getting started with AAP guide (#2358)

hherbly · web-flow · commit 3790a4fb5d7b · 2024-10-15T17:04:29.000-06:00
* link fixes in gs with aap guide

* fixes broken links throughout guide

* further cleanup
diff --git a/downstream/assemblies/platform/assembly-gs-auto-dev.adoc b/downstream/assemblies/platform/assembly-gs-auto-dev.adoc
@@ -27,7 +27,7 @@ include::platform/con-gs-setting-up-dev-env.adoc[leveloffset=+1]
 include::platform/con-gs-create-automation-content.adoc[leveloffset=+1]
 include::platform/con-gs-define-events-rulebooks.adoc[leveloffset=+1]
 include::platform/con-gs-ansible-roles.adoc[leveloffset=+1]
-include::platform/proc-gs-creating-a-role.adoc[leveloffset=+1]
+include::platform/proc-creating-ansible-role.adoc[leveloffset=+2]
 include::platform/con-gs-learn-about-collections.adoc[leveloffset=+1]
 include::platform/proc-gs-publish-to-a-collection.adoc[leveloffset=+1]
 include::platform/proc-gs-upload-collection.adoc[leveloffset=+2]
@@ -39,11 +39,11 @@ include::platform/proc-gs-auto-dev-set-up-decision-env.adoc[leveloffset=+2]
 include::platform/proc-gs-auto-dev-create-automation-execution-proj.adoc[leveloffset=+1]
 include::platform/proc-gs-auto-dev-create-automation-decision-proj.adoc[leveloffset=+1]
 include::platform/con-gs-auto-dev-about-inv.adoc[leveloffset=+1]
-include::platform/proc-controller-create-inventory.adoc[leveloffset=+2]
+// [hherbly] this repeats module above include::platform/proc-controller-create-inventory.adoc[leveloffset=+2]
 include::platform/con-gs-auto-dev-job-templates.adoc[leveloffset=+1]
 include::platform/proc-controller-getting-started-with-job-templates.adoc[leveloffset=+2]
 include::platform/proc-gs-auto-dev-create-template.adoc[leveloffset=+2]
-include::platform/proc-gs-auto-dev-run-template.adoc[leveloffset=+2]
+// [hherbly] incomplete module? include::platform/proc-gs-auto-dev-run-template.adoc[leveloffset=+2]
 include::platform/proc-controller-edit-job-template.adoc[leveloffset=+2]
 include::platform/con-gs-rulebook-activations.adoc[leveloffset=+1]
 include::platform/proc-gs-eda-set-up-rulebook-activation.adoc[leveloffset=+2]
diff --git a/downstream/assemblies/platform/assembly-gs-auto-op.adoc b/downstream/assemblies/platform/assembly-gs-auto-op.adoc
@@ -31,7 +31,7 @@ include::platform/con-gs-ansible-roles.adoc[leveloffset=+1]
 include::platform/proc-creating-ansible-role.adoc[leveloffset=+2]
 include::platform/con-gs-ansible-content.adoc[leveloffset=+1]
 include::platform/con-gs-learn-about-collections.adoc[leveloffset=+2]
-include::platform/proc-gs-browse-content.adoc[leveloffset=+2]
+// [hherbly] removing because it repeats modules above include::platform/proc-gs-browse-content.adoc[leveloffset=+2]
 include::platform/proc-gs-downloading-content.adoc[leveloffset=+2]
 //
 include::platform/proc-gs-publish-to-a-collection.adoc[leveloffset=+1]
diff --git a/downstream/modules/platform/con-gs-ansible-roles.adoc b/downstream/modules/platform/con-gs-ansible-roles.adoc
@@ -6,15 +6,4 @@ A role is like a customized piece of automation content that bundles together re
 
 Instead of creating huge playbooks with hundreds of tasks, you can use roles to break the tasks apart into smaller, more discrete units of work. 
 
-To learn more about roles, see link:https://www.redhat.com/en/topics/automation/what-is-an-ansible-role#why-use-a-role-instead-of-a-playbook[What is an Ansible Role-and how is it used?].
-
-== Creating a role
-
-You can create roles using the Ansible Galaxy CLI tool, which is included with your {PlatformNameShort} bundle. Access role-specific commands from the roles subcommand:
-
-[source,bash]
-----
-ansible-galaxy role init <role_name>
-----
-
-Standalone roles outside of collections are still supported, but we recommend that you create new roles inside of a collection to take advantage of all the features {PlatformNameShort} has to offer.
+To learn more about roles, see link:https://www.redhat.com/en/topics/automation/what-is-an-ansible-role[What is an Ansible Role-and how is it used?].
diff --git a/downstream/modules/platform/con-gs-auto-dev-about-inv.adoc b/downstream/modules/platform/con-gs-auto-dev-about-inv.adoc
@@ -18,7 +18,7 @@ Use the following procedure to create a new inventory.
 * *Name*: Enter a name for the inventory.
 * Optional: *Description*: Enter a description.
 * *Organization*: Choose among the available organizations. 
-* Only applicable to Smart Inventories: *Smart Host Filter*:  Filters are similar to tags in that tags are used to filter certain hosts that contain those names. Therefore, to populate this field, specify a tag that contains the hosts you want, not the hosts themselves. Filters are case-sensitive. For more information, see link:{URLControllerUserGuide}/index#ref-controller-smart-host-filter[Smart host filters] in the {TitleControllerUserGuide} guide.
+* Only applicable to Smart Inventories: *Smart Host Filter*:  Filters are similar to tags in that tags are used to filter certain hosts that contain those names. Therefore, to populate this field, specify a tag that contains the hosts you want, not the hosts themselves. Filters are case-sensitive. For more information, see link:{URLControllerUserGuide}/controller-inventories#ref-controller-smart-host-filter[Smart host filters] in the {TitleControllerUserGuide} guide.
 * *Instance groups*: Select the instance group or groups for this inventory to run on. If the list is extensive, use the search to narrow the options. You can select multiple instance groups and sort them in the order that you want them run.
 * Optional: *Labels*: Add labels that describe this inventory, so they can be used to group and filter inventories and jobs.
 * Only applicable to constructed inventories: *Input inventories*: Specify the source inventories to include in this constructed inventory. Empty groups from input inventories are copied into the constructed inventory.
@@ -27,7 +27,7 @@ Use the following procedure to create a new inventory.
 ** Verbose logging includes the output of all commands. 
 ** Debug logging is exceedingly verbose and includes information on SSH operations that can be useful in certain support instances. Most users do not need to see debug mode output.
 * Only applicable to constructed inventories: *Limit*: Restricts the number of returned hosts for the inventory source associated with the constructed inventory. You can paste a group name into the limit field to only include hosts in that group. For more information, see the *Source variables* setting.
-* Only applicable to standard inventories: *Options*: Check the box next to *Prevent instance group fallback* to enable only the instance groups listed in the *Instance groups* field to execute the job. If unchecked, all available instances in the execution pool will be used based on the hierarchy described in link:{URLControllerAdminGuide}/controller-instance-and-container-groups#controller-control-job-run[Control where a job runs] in the {TitleControllerAdminGuide} guide. Click the tooltip for more information.
+* Only applicable to standard inventories: *Options*: Check the box next to *Prevent instance group fallback* to enable only the instance groups listed in the *Instance groups* field to execute the job. If unchecked, all available instances in the execution pool will be used based on the hierarchy described in link:{URLControllerAdminGuide}/controller-clustering#controller-cluster-job-runs[Control where a job runs] in the {TitleControllerAdminGuide} guide. Click the tooltip for more information.
 +
 NOTE: Set the `prevent_instance_group_fallback` option for smart inventories through the API. 
 +
diff --git a/downstream/modules/platform/con-gs-auto-op-execute-inv.adoc b/downstream/modules/platform/con-gs-auto-op-execute-inv.adoc
@@ -15,5 +15,5 @@ The *Inventories* window displays a list of inventories that are currently avail
 * *Organization*: The organization to which the inventory belongs. 
 . Select an inventory name to display the *Details* page for the inventory, including the inventory's groups and hosts.
 
-For more information about inventories, see the link:{URLControllerUserGuide}/index#controller-inventories[Inventories] section of the {TitleControllerUserGuide} guide.
+For more information about inventories, see the link:{URLControllerUserGuide}/controller-inventories[Inventories] section of the {TitleControllerUserGuide} guide.
 
diff --git a/downstream/modules/platform/con-gs-auto-op-job-templates.adoc b/downstream/modules/platform/con-gs-auto-op-job-templates.adoc
@@ -4,6 +4,6 @@
 
 A job template is a definition and set of parameters for running an Ansible job.
 
-A job template combines an Ansible Playbook from a project with the settings required to launch the job. Job templates are useful for running the same job many times. Job templates also encourage the reuse of Ansible Playbook content and collaboration between teams. For more information, see link:{URLControllerUserGuide}/index#controller-job-templates[Job Templates] in the {TitleControllerUserGuide} guide.
+A job template combines an Ansible Playbook from a project with the settings required to launch the job. Job templates are useful for running the same job many times. Job templates also encourage the reuse of Ansible Playbook content and collaboration between teams. For more information, see link:{URLControllerUserGuide}/controller-job-templates[Job Templates] in the {TitleControllerUserGuide} guide.
 
 Platform administrators and automation developers have the permissions to create job templates. As an automation operator you can launch job templates and view their details.
diff --git a/downstream/modules/platform/con-gs-learn-about-collections.adoc b/downstream/modules/platform/con-gs-learn-about-collections.adoc
@@ -7,21 +7,6 @@ Ansible content collections are assemblages of automation content. There are two
 * *{CertifiedName}*, which contain fully-supported roles and modules that are enterprise- and production-ready for use in your environments.
 * *{Valid} collections*, which provide you with a trusted, expert-guided approach for performing foundational operations and tasks in your product. 
 
-Both types of content collections can be found in {HubName} through the link:{Console}[Hybrid Cloud Console].
+Both types of content collections can be found in {HubName} through the link:https://console.redhat.com/ansible/automation-hub/[Hybrid Cloud Console].
 
-== Downloading content 
-
-After collections are finalized, you can import them to a location where they can be distributed to others across your organization.
-
-.Procedure
-
-. Log in to {PlatformName}.
-. From the navigation panel, select {MenuACCollections}. 
-The *Collections* page displays all collections across all repositories. 
-You can search for a specific collection.
-. Select the collection that you want to export. 
-The collection details page opens.
-. From the *Install* tab, select *Download tarball*. 
-The .tar file is downloaded to your default browser downloads folder. 
-You can now import it to the location of your choosing.
 
diff --git a/downstream/modules/platform/proc-creating-ansible-role.adoc b/downstream/modules/platform/proc-creating-ansible-role.adoc
@@ -4,6 +4,11 @@
 
 You can create roles using the {Galaxy} CLI tool, which is included with your {PlatformNameShort} bundle. Access role-specific commands from the `role` subcommand:
 
+[source,bash]
+----
+ansible-galaxy role init <role_name>
+----
+
 Standalone roles outside of Collections are supported.
 Create new roles inside a Collection to take advantage of the features {PlatformNameShort} has to offer.
 
@@ -50,6 +55,3 @@ $ ansible-galaxy role init my_role --role-skeleton ~/role_skeleton
 +
 This creates a role named `my_role` by copying the contents of `~/role_skeleton` into `my_role`.
 The contents of `role_skeleton` can be any files or folders that are valid inside a role directory.
-
-For more information on creating roles, see [Aine’s new devtools content].
-
diff --git a/downstream/modules/platform/proc-gs-add-ee-to-job-template.adoc b/downstream/modules/platform/proc-gs-add-ee-to-job-template.adoc
@@ -4,7 +4,7 @@
 
 .Prerequisites
 
-* An {ExecEnvShort} must have been created using ansible-builder as described in link:{URLBuilder}/index#assembly-using-builder[Using {Builder}]. 
+* An {ExecEnvShort} must have been created using ansible-builder as described in link:{URLBuilder}/assembly-using-builder[Using {Builder}]. 
 When an {ExecEnvShort} has been created, you can use it to run jobs. 
 Use the {ControllerName} UI to specify the execution environment to use in your job templates.
 * Depending on whether an {ExecEnvShort} is made available for global use or tied to an organization, you must have the appropriate level of administrator privileges to use an {ExecEnvShort} in a job. 
@@ -38,4 +38,4 @@ When you have added an {ExecEnvShort} to a job template, the template will be li
 
 If you have many {ExecEnvShort} that you want to maintain, you can store them in a container registry linked to your {PrivateHubName}. 
 
-For more information, see link:{URLBuilder}/index#populate-container-registry[Populating your private automation hub container registry] from the {TitleBuilder} guide.  
+For more information, see link:{URLBuilder}/populate-container-registry[Populating your private automation hub container registry] from the {TitleBuilder} guide.  
diff --git a/downstream/modules/platform/proc-gs-auto-dev-create-automation-execution-proj.adoc b/downstream/modules/platform/proc-gs-auto-dev-create-automation-execution-proj.adoc
@@ -9,25 +9,21 @@ You can set up an automation execution project in the platform UI.
 
 .Procedure
 
-Procedure
 . From the navigation panel, select {MenuAEProjects}.
 . On the *Projects* page, click btn:[Create project] to launch the *Create Project* window.
-+
-//image:projects-create-new-project.png[Projects- create new project]
-
 . Enter the appropriate details into the following required fields:
 
 * *Name* (required)
 * Optional: *Description*
 * *Organization* (required): A project must have at least one organization. Select one organization now to create the project. When the project is created you can add additional organizations.
 * Optional: *Execution Environment*: Enter the name of the {ExecEnvShort} or search from a list of existing ones to run this project.
-For more information, see link:{URLUpgrade}/upgrading-to-ees[Migrating to automation execution environments] in the {TitleUpgrade}.
 * *Source Control Type* (required): Select an SCM type associated with this project from the menu.
 Options in the following sections become available depending on the type chosen.
-For more information, see link:{URLControllerUserGuide}/index#proc-projects-manage-playbooks-manually[Managing playbooks manually] or link:{URLControllerUserGuide}/index#ref-projects-manage-playbooks-with-source-control[Managing playbooks using source control].
+For more information, see link:{URLControllerUserGuide}/controller-projects#proc-controller-adding-a-project[Managing playbooks manually] or link:{URLControllerUserGuide}/controller-projects#ref-projects-manage-playbooks-with-source-control[Managing playbooks using source control].
 * Optional: *Content Signature Validation Credential*: Use this field to enable content verification.
 Specify the GPG key to use for validating content signature during project synchronization.
 If the content has been tampered with, the job will not run.
-For more information, see link:{URLControllerUserGuide}/index#assembly-controller-project-signing[Project signing and verification].
+For more information, see link:{URLControllerUserGuide}/assembly-controller-project-signing[Project signing and verification].
++
 . Click btn:[Create project].
 
diff --git a/downstream/modules/platform/proc-gs-auto-dev-create-template.adoc b/downstream/modules/platform/proc-gs-auto-dev-create-template.adoc
@@ -56,7 +56,7 @@ Choose the credential from the available options to use with this job template.
 Use the drop-down menu list to filter by credential type if the list is extensive.
 Some credential types are not listed because they do not apply to certain job templates. a|
 - If selected, when launching a job template that has a default credential and supplying another credential replaces the default credential if it is the same type.
-The following is an example this message:
+The following is an example of this message:
 
 `Job Template default credentials must be replaced
 with one of the same type. Please select a credential
@@ -111,9 +111,9 @@ For more information about job slices, see link:{URLControllerUserGuide}/control
 - A timeout of 0 on a job template defaults the job to the global timeout (which is no timeout by default).
 - A positive timeout sets the timeout for that job template. | Yes
 | Show Changes | Enables you to see the changes made by Ansible tasks. | Yes
-| Instance Groups | Choose link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html/automation_controller_administration_guide/controller-instance-and-container-groups[Instance and Container Groups] to associate with this job template.
+| Instance Groups | Choose link:{URLControllerUserGuide}/controller-instance-and-container-groups#controller-instance-group-policies[Instance and Container Groups] to associate with this job template.
 If the list is extensive, use the image:examine.png[examine,15,15] icon to narrow the options.
-Job template instance groups contribute to the job scheduling criteria, see link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html/automation_controller_administration_guide/controller-instance-and-container-groups#controller-job-runtime-behavior[Job Runtime Behavior] and link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html/automation_controller_administration_guide/controller-instance-and-container-groups#controller-control-job-run[Control where a job runs] for rules.
+Job template instance groups contribute to the job scheduling criteria, see link:{URLControllerUserGuide}/assembly-controller-topology-viewer#controller-job-runtime-behavior[Job Runtime Behavior] and link:{URLControllerAdminGuide}controller-clustering#controller-cluster-job-runtime[Control where a job runs] for rules.
 A System Administrator must grant you or your team permissions to be able to use an instance group in a job template.
 Use of a container group requires admin rights. a| - Yes.
 
@@ -144,7 +144,7 @@ This is the equal of passing the `--become` option to the `ansible-playbook` com
 For more information, see link:{URLControllerUserGuide}/controller-job-templates#controller-provisioning-callbacks[Provisioning Callbacks].
 * *Enable webhook*: If checked, you turn on the ability to interface with a predefined SCM system web service that is used to launch a job template.
 GitHub and GitLab are the supported SCM systems.
-** If you enable webhooks, other fields display, prompting for additional information:
+If you enable webhooks, other fields display, prompting for additional information:
 +
 //image::ug-job-templates-options-webhooks.png[Job templates webhooks]
 +
@@ -161,7 +161,7 @@ See link:{URLControllerUserGuide}/controller-credentials#ref-controller-credenti
 * *Concurrent jobs*: If checked, you are allowing jobs in the queue to run simultaneously if not dependent on one another. Check this box if you want to run job slices simultaneously. For more information, see link:{URLControllerUserGuide}/controller-jobs#controller-capacity-determination[{ControllerNameStart} capacity determination and job impact].
 * *Enable fact storage*: If checked, {ControllerName} stores gathered facts for all hosts in an inventory related to the job running.
 * *Prevent instance group fallback*: Check this option to allow only the instance groups listed in the *Instance Groups* field to run the job.
-If clear, all available instances in the execution pool are used based on the hierarchy described in link:{BaseURL}/red_hat_ansible_automation_platform/{PlatformVers}/html-single/automation_controller_administration_guide/index[Control where a job runs].
+If clear, all available instances in the execution pool are used based on the hierarchy described in link:{URLControllerAdminGuide}controller-clustering#controller-cluster-job-runtime[Control where a job runs].
 . Click btn:[Create job template], when you have completed configuring the details of the job template.
 
 Creating the template does not exit the job template page but advances to the Job Template *Details* tab.
diff --git a/downstream/modules/platform/proc-gs-auto-op-launch-template.adoc b/downstream/modules/platform/proc-gs-auto-op-launch-template.adoc
@@ -16,5 +16,5 @@ The *Templates* list view shows job templates that are currently available. The
 
 From this screen you can launch, edit, and copy a job template. 
 
-For more information about templates see the link:{URLControllerUserGuide}/index#controller-job-templates[Job templates] and link:{URLControllerUserGuide}/index#controller-workflow-job-templates[Workflow job templates] sections of the {TitleControllerUserGuide}.
+For more information about templates see the link:{URLControllerUserGuide}/controller-job-templates[Job Templates] and link:{URLControllerUserGuide}/controller-workflow-job-templates[Workflow job templates] sections of the {TitleControllerUserGuide} guide.
 
diff --git a/downstream/modules/platform/proc-gs-eda-set-up-rulebook-activation.adoc b/downstream/modules/platform/proc-gs-eda-set-up-rulebook-activation.adoc
diff --git a/downstream/modules/platform/proc-gs-publish-to-a-collection.adoc b/downstream/modules/platform/proc-gs-publish-to-a-collection.adoc
diff --git a/downstream/modules/platform/proc-gs-write-playbook.adoc b/downstream/modules/platform/proc-gs-write-playbook.adoc
