I don't believe it
This commit is contained in:
@@ -190,3 +190,27 @@ To do that you can simply run `python3 secdep.py -P aws --awsregion <region> -a
|
||||
If you can, prefer a better ssh client.
|
||||
|
||||
To SSH into a virtual machine you get the choice from `python3 secdep.py -ssh` or `python3 secdep.py -P gce -ssh` to only choose from the gce instances.
|
||||
|
||||
# Generating shell completion scripts 🐚
|
||||
|
||||
To generate shell completion scripts you can run
|
||||
|
||||
`python3 secdep.py --print-completion zsh`
|
||||
|
||||
or
|
||||
|
||||
`python3 secdep.py --print-completion bash`
|
||||
|
||||
according to your shell of choice.
|
||||
|
||||
To use the completion scripts you need to put them in the right place for each shell after we save the output to a file.
|
||||
|
||||
For example, if you are using zsh and you aliased the command to `secdep` you can run
|
||||
|
||||
`secdep --print-completion zsh > _secdep && sudo mv _secdep /usr/share/zsh/site-functions`
|
||||
|
||||
Then when you reload your shell you can use the completion scripts.
|
||||
|
||||
For bash the command would be `secdep --print-completion bash > secdep && sudo mv secdep /etc/bash_completion.d`
|
||||
|
||||
Then make sure in your `.bashrc` or `.bash_profile` you have `source /etc/bash_completion.d/secdep` and reload your shell
|
||||
|
||||
Reference in New Issue
Block a user