Add run shell command playbook

[firyx]

PULL REQUEST

Overview

Adding a playbook to run ad-hoc shell commands against the portals.

Example for Visual Changes

Checklist

• [x] All git commits are signed. (REQUIRED)
• [x] All new methods or updated methods have clear docstrings.
• [x] Testing added or updated for new methods.
• [x] Verified if any changes impact the WebPortal Health Checks.
• [x] Appropriate documentation updated.
• [x] Changelog file created.

Issues Closed

[linear[bot]]

SKY-943 Create run shell command playbook

[firyx]

Is there a way we can combine this with the docker commands? Very similar, potentially the same, if the docker command variable was named better. My bad grimacing

Is there a way we can combine this with the docker commands? Very similar, potentially the same, if the docker command variable was named better. My bad grimacing

Refactored to unite docker/shell commands. There are now 2 distinct playbooks to run shell commands - safer with and less safer without taking portals out of LB. Described in updated Readme.

[firyx]

@kwypchlo Once this is merged and changes are pulled, we should update docker_commands to shell_commands in deploy-2022-... configs.

[firyx]

Backwards compatibility (no change to existing configs is needed):

• at least one of: older docker_commands or newer shell_commands must be defined
• when both are defined: Ansible adds those 2 lists and runs all commands

[kwypchlo]

Backwards compatibility (no change to existing configs is needed):

• at least one of: older docker_commands or newer shell_commands must be defined
• when both are defined: Ansible adds those 2 lists and runs all commands

hold up, what do you mean at least one has to be defined? defining additional commands should be really optional right?

[firyx]

Backwards compatibility (no change to existing configs is needed):

• at least one of: older docker_commands or newer shell_commands must be defined
• when both are defined: Ansible adds those 2 lists and runs all commands

hold up, what do you mean at least one has to be defined? defining additional commands should be really optional right?

My bad (incomplete) wording:

• There are 2 playbooks when you explicitly want to run docker/shell commands. For these 2 playbooks you must explicitly set either docker_commands or shell_commands, otherwise you have something misconfigured - e.g. you forget to load the vars file -e @my-vars/....
• For deployment playbooks docker_commands and shell_commands are optional.

[kwypchlo]

not on a current roadmap