Terms
Summary
Extend the dependency checks the trellis check command carries out to include required provisioning/deployment checks like SSH agent, keys, Ansible.
Motivation
Why are we doing this?
Right now, trellis check looks for Python, Vagrant and Virtualbox compatibility related to local development, but some important checks would be:
- system Ansible version and its compatibility
- SSH agent being enabled
- SSH agent keys being loaded
What use cases does it support?
Would be nice to support checks of any known dependencies of the deploy/provision processes.
What is the expected outcome?
An output like:
Checking Trellis requirements...
Required:
[✓] Ansible [>= 2.9.7]: 2.10.0
[✓] Python [>= 3.8.0]: 3.11.2
[✓] SSH Agent [On]: Yes
[✓] SSH Agent [Loaded]: Yes
Optional:
[✓] Vagrant [>= 2.1.0]: 2.3.4
[✓] VirtualBox [>= 4.3.10]: 6.1.36r152435
...
Potential conflicts / foreseeable issues
May conflict with Ansible version in virtual environment
Additional Context
No response
Terms
Summary
Extend the dependency checks the
trellis checkcommand carries out to include required provisioning/deployment checks like SSH agent, keys, Ansible.Motivation
Why are we doing this?
Right now,
trellis checklooks for Python, Vagrant and Virtualbox compatibility related to local development, but some important checks would be:What use cases does it support?
Would be nice to support checks of any known dependencies of the deploy/provision processes.
What is the expected outcome?
An output like:
Potential conflicts / foreseeable issues
May conflict with Ansible version in virtual environment
Additional Context
No response