readme/how
This commit is contained in:
parent
0d88199302
commit
ca347bd626
1 changed files with 26 additions and 3 deletions
29
readme.md
29
readme.md
|
@ -14,11 +14,34 @@ What if there was a unified way to do so?
|
|||
|
||||
## How
|
||||
|
||||
Picture it…
|
||||
|
||||
### Group environment variables
|
||||
|
||||
* numbered
|
||||
* Certificate Authority armored certificates
|
||||
* Domain Name System servers IP addresses
|
||||
* set group environment variables for
|
||||
* ref names for deployment contexts of feature, staging & release
|
||||
* alternate locations of
|
||||
* Git repositories of this project & its parent framework
|
||||
* Operating Systems & Software packages
|
||||
* SSH key & hosts for deployments
|
||||
* a standalone POSIX shell script payload
|
||||
|
||||
### Workflow files
|
||||
|
||||
* calling the POSIX shell script payload as their very first step
|
||||
* using a unified YAML syntax made of actions implemented in Python
|
||||
|
||||
### Continous Integration & Deployment
|
||||
|
||||
* configuring the Operating System container
|
||||
* installing Python system & virtual environments
|
||||
|
||||
## What
|
||||
|
||||
Handle project workflows
|
||||
* from a POSIX shell script payload in a group variable
|
||||
* with a unified YAML syntax of actions implemented in Python
|
||||
Handle project workflows:
|
||||
* whether the network infrastructure is
|
||||
* [X] online
|
||||
* [X] offline with custom
|
||||
|
|
Loading…
Reference in a new issue