Update CI badges in README.md (#1218)

* Update CI badges in README.md

* fix markdown links

* fix authentication link

* export fix

* fix credential docs

Author: sean-m-sullivan

README.md

@@ -1,7 +1,7 @@
 # Red Hat Communities of Practice AAP Configuration Collection
 
-![pre-commit tests](https://github.com/redhat-cop/aap_configuration/actions/workflows/pre-commit.yml/badge.svg)
-![Release](https://github.com/redhat-cop/aap_configuration/actions/workflows/release.yml/badge.svg)
+[![pre-commit tests](https://github.com/redhat-cop/infra.aap_configuration/actions/workflows/pre-commit.yml/badge.svg)](https://github.com/redhat-cop/infra.aap_configuration/actions/workflows/pre-commit.yml)
+[![Release - Automated](https://github.com/redhat-cop/infra.aap_configuration/actions/workflows/release_auto.yml/badge.svg)](https://github.com/redhat-cop/infra.aap_configuration/actions/workflows/release_auto.yml)
 <!-- markdownlint-disable-line MD033 MD034 --><a href="https://raw.githubusercontent.com/redhat-cop/infra.aap_configuration/devel/docs/aap_config_as_code_public_meeting.ics"><img border="0" alt="Google Calendar invite" width="60" src="https://ssl.gstatic.com/calendar/images/dynamiclogo_2020q4/calendar_20_2x.png"></a>
 <!-- Further CI badges go here as above -->
 
@@ -111,7 +111,7 @@ You can also specify authentication by a combination of either:
 * `aap_hostname`, `aap_token`
 
 The OAuth2 token is the preferred method. You can obtain the token through the preferred `controller_token` module, or through the
-AWX CLI [login](https://docs.ansible.com/automation-controller/latest/html/controllerapi/authentication.html)
+AWX CLI [login](https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/automation_execution_api_overview/controller-api-auth-methods)
 command.
 
 These can be specified via (from highest to lowest precedence):

changelogs/fragments/trivial_stuff.yml

@@ -3,4 +3,5 @@ trivial:
   - Adding back Brant Evans @branic as a major contributor to the collection. (unsure how this got removed)
   - Updated readme license links
   - Updated markdownlint related settings
+  - Updated status badges on main Readme
 ...

docs/EXPORT_README.md

@@ -6,7 +6,7 @@ This is documentation on how to use a the Automation Controller export commands
 
 This command allows exporting all available endpoints for Automation Controller for use in importing, templates, backups and many other uses.
 
-**NOTE:** If you use the awx export option it will NOT use the correct high level variable list naming that is expected by the rest of these roles you will need to correctly name them before being able to use the roles to import the data into your new Controller. See [#332](https://github.com/redhat-cop/aap_configuration/issues/332) for more details.
+**NOTE:** If you use the awx export option it will NOT use the correct high level variable list naming that is expected by the rest of these roles you will need to correctly name them before being able to use the roles to import the data into your new Controller. See [#332](https://github.com/redhat-cop/infra.aap_configuration/issues/332) for more details.
 
 ## Installation
 

roles/controller_credential_input_sources/README.md

@@ -80,7 +80,7 @@ This also speeds up the overall role.
 |`description`|""|no|str|Description to use for the credential input source.|
 |`state`|`present`|no|str|Desired state of the resource.|
 
-For further details on fields see <https://docs.ansible.com/automation-controller/latest/html/userguide/credential_plugins.html>. The input accepted by the `metadata` field will differ depending on the credential plugin being used.
+For further details on fields see <https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/configuring_automation_execution/assembly-controller-secret-management>. The input accepted by the `metadata` field will differ depending on the credential plugin being used.
 
 ### Standard Credential Input Source Data Structure
 

roles/eda_credential_types/README.md

@@ -72,7 +72,7 @@ Example:
 
 Because of this it is difficult to provide controller with the required format for these fields.
 
-The workaround is easier to do in yaml with unsafe syntax, to read more about this check out the [documentation](https://docs.ansible.com/ansible/latest/user_guide/playbooks_advanced_syntax.html):
+The workaround is easier to do in yaml with unsafe syntax, to read more about this check out the [documentation](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_advanced_syntax.html):
 
 ```yaml
 !unsafe '{{ variable }}'