getstackhead / stackhead-cli Goto Github PK

Ansible Plugins from StackHead modules should be autoloaded when using the StackHead CLI.
The paths should be set in a generated ansible.cfg file used for Ansible commands.

The CLI integration tests fails at the "tear down project" step for unknown reasons.
The playbook test worked fine so far.

Add setting to CLI config file to allow configuring the email address used for ACME certificate registration.
The variable was already added in StackHead next: getstackhead/stackhead@81675b8

Running ./stackhead-cli init will not install StackHead to the actual Ansible collection location but inside the folder this command is called and replicate the structure there.

E.g. /home/mario/Workspace/projects/ /home/mario/.ansible/collections/ansible_collections
instead of /home/mario/.ansible/collections/ansible_collections

A CLI wrapper can make it easier to use StackHead, especially when modularity comes into play.
This would also allow to have a non-Ansible bound StackHead configuration file separate from the Ansible inventory.

• https://github.com/spf13/cobra
• https://github.com/briandowns/spinner

Possible commands:

• stackhead setup: Setup single server (server-provision.yml)
• stackhead check: Check versions on a server (server-check.yml)
• stackhead deploy: Deploy a single project (application-deploy.yml)
• stackhead destroy: Destroy a single project (application-destroy.yml)
• stackhead init: Initialize StackHead dependencies from StackHead configuration file
• stackhead validate: Validate a project definition file

StackHead configuration file

Allows configuring the webserver and container to use.
Default values of those will be set on CLI level, removing the dependencies from the Ansible role.

Running stackhead init will install all requirements and roles. Requires Ansible to already be installed!