konsthol/SecDep
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed a little bug...

Browse Source
This commit is contained in:
konsthol
2023-09-25 06:07:39 +03:00
parent b90cdb3761
commit 68983889d3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
assets/pages/tips_tricks/tips_n_tricks.md
View File

@@ -64,7 +64,7 @@ Example usage:
`secdep -P aws -a deleteall --awsregion us-east-2` `secdep -P aws -a deleteall --awsregion us-east-2`
## Usage with Ansible 🤖 goes hand in hand <img src="../../../assets/videos/handshake.gif" height="32px"/> ## Usage with Ansible 🤖 goes hand in hand<img src="../../../assets/videos/handshake.gif" height="32px"/>
If you have Ansible installed, you can use the hosts file generated by SecDep to run commands on all of the instances simultaneously. If you have Ansible installed, you can use the hosts file generated by SecDep to run commands on all of the instances simultaneously.
This file is located in the SecDep directory and is being updated every time you create or delete an instance. All instances have a secdep user created and you automatically have an ssh key to use for the connection so you can easily use Ansible to run commands to all of them. If you have Ansible playbooks you wish to run on fresh installations you should create the instances without the `--deploy` flag. This file is located in the SecDep directory and is being updated every time you create or delete an instance. All instances have a secdep user created and you automatically have an ssh key to use for the connection so you can easily use Ansible to run commands to all of them. If you have Ansible playbooks you wish to run on fresh installations you should create the instances without the `--deploy` flag.