Skip to content

AAP-66350 updated docs to automate deletion of clusters.yaml #5631

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.

Sign up for GitHub

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

Open
emurtoug wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −6
Open

AAP-66350 updated docs to automate deletion of clusters.yaml #5631

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions downstream/modules/automation-dashboard/proc-integrating-automation-dashboard.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,16 +94,21 @@ The `access_token`, `refresh_token`, and `client_secret` are stored in the {Auto
These values are encrypted for security.
====

. Load and activate your {AutomationDashboardName} configuration:
. Load and activate your {AutomationDashboardName} configuration. You must copy the configuration file to the container’s `/tmp/` directory. The system automatically removes the file from the container after successful processing.
+
[source,bash]
----
podman cp clusters.yaml automation-dashboard-web:/
podman exec -it automation-dashboard-web /venv/bin/python manage.py setclusters /clusters.yaml
podman cp clusters.yaml automation-dashboard-web:/tmp
podman exec -it automation-dashboard-web /venv/bin/python manage.py setclusters /tmp/clusters.yaml
----
+
[NOTE]
====
If the system cannot remove the file from the /tmp/ directory, it displays an error message and continues running.
====
+
[NOTE]
====
**Token Rotation:** The {AutomationDashboardName} rotates tokens internally for security but does not update your local `clusters.yaml` file. If you must re-run the `setclusters` command later, your defined tokens might be expired.

To retrieve the current valid tokens, run the following command and save the output to a new file:
Expand Down
6 changes: 3 additions & 3 deletions downstream/modules/automation-dashboard/proc-upgrading-automation-dashboard.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,12 +57,12 @@ ansible-playbook -i inventory ansible.containerized_installer.dashboard_install
For instructions on obtaining these values, see link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/{PlatformVers}/html-single/using_automation_dashboard/index#proc-integrating-automation-dashboard[Integrating {AutomationDashboardName} with your {PlatformNameShort}].
====

. Apply the updated configuration to the dashboard:
. Apply the updated configuration to the dashboard. You must copy the configuration file to the container's `/tmp/` directory:
+
[source,bash]
----
podman cp clusters.yaml automation-dashboard-web:/
podman exec -it automation-dashboard-web /venv/bin/python manage.py setclusters /clusters.yaml
podman cp clusters.yaml automation-dashboard-web:/tmp/
podman exec -it automation-dashboard-web /venv/bin/python manage.py setclusters /tmp/clusters.yaml
----

.Verification
Expand Down