- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Wed, Mar 25
Two actions to fix:
The nginx configuration doesn't seem the same for the Docker container and the development site:
Tue, Mar 24
The script to test if we can access to the OVH credentials (application_key, application_secret, consumer_key):
The script to test the connection to Vault, using a YAML configuration file that tells the secretsmith client how to connect to Vault :
It is not necessary to create a local map.jinja here, since it only imports a variable from the global map.jinja.
- Install pip using the OS-specific package prefix from map.jinja.
Mon, Mar 23
ovh and secretsmith are now installed on the router-002 and router-003.
1.Add map to avoid to hunt version every time we update python.
removed canonical ipv4 from network.sls and corrected node function
better variable name
removed for loop
testing list format for routers
I've asked upstream for advice how to resolve pillar for another server than the current node @ https://groups.google.com/g/salt-tower/c/XEKg2CEiZrU
added router parameter
Light modifications
The output is really useful to avoid to manually repeat the ports.
Rebased. Fixed pillar handling.
In D4026#62889, @dereckson wrote:Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.