[GH-ISSUE #62] Two hyphen to much on autocompletion #16

New issue

Closed

opened 2026-05-07 00:17:29 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-07 00:17:29 +02:00

Owner

Originally created by @dwydler on GitHub (Nov 22, 2020).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/62

Hello,
i typed adminSudo and press that two times the key. The first parameter is displayed with four hyphen.

---bs-server----------------------------------------------the-bastion-3.01.00---
----------------------------------------------------------------------</help>---
administrator@bastionhost01(master)> adminSudo -- --sudo-as

Originally created by @dwydler on GitHub (Nov 22, 2020). Original GitHub issue: https://github.com/ovh/the-bastion/issues/62 Hello, i typed adminSudo and press that two times the <TAB> key. The first parameter is displayed with four hyphen. ``` ---bs-server----------------------------------------------the-bastion-3.01.00--- ----------------------------------------------------------------------</help>--- administrator@bastionhost01(master)> adminSudo -- --sudo-as ```

BreizhHardware closed this issue

2026-05-07 00:17:29 +02:00

BreizhHardware commented

2026-05-07 00:17:30 +02:00

Author

Owner

@speed47 commented on GitHub (Nov 23, 2020):

adminSudo is a bit special, the first double-dash is corrrect, as explained in the adminSudo --help message:

~ Impersonate another user
~ 
~ Usage: --osh adminSudo -- --sudo-as ACCOUNT <--sudo-cmd PLUGIN -- [PLUGIN specific options...]>
~ 
~   --sudo-as ACCOUNT  Specify which bastion account we want to impersonate
~   --sudo-cmd PLUGIN  --osh command we want to launch as the user (see --osh help)
~ 
~ Example::
~ 
~   --osh adminSudo -- --sudo-as user12 --sudo-cmd info -- --name somebodyelse
~ 
~ Don't forget the double-double-dash as seen in the example above: one after the plugin name,
~ and another one to separate adminSudo options from the options of the plugin to be called.

This is to ensure the proper options are parsed by the proper stage of execution, because under the hood, you're sudo'ing to the target user, and executing osh.pl again under their name

@speed47 commented on GitHub (Nov 23, 2020): `adminSudo` is a bit special, the first double-dash is corrrect, as explained in the `adminSudo --help` message: ``` ~ Impersonate another user ~ ~ Usage: --osh adminSudo -- --sudo-as ACCOUNT <--sudo-cmd PLUGIN -- [PLUGIN specific options...]> ~ ~ --sudo-as ACCOUNT Specify which bastion account we want to impersonate ~ --sudo-cmd PLUGIN --osh command we want to launch as the user (see --osh help) ~ ~ Example:: ~ ~ --osh adminSudo -- --sudo-as user12 --sudo-cmd info -- --name somebodyelse ~ ~ Don't forget the double-double-dash as seen in the example above: one after the plugin name, ~ and another one to separate adminSudo options from the options of the plugin to be called. ``` This is to ensure the proper options are parsed by the proper stage of execution, because under the hood, you're `sudo`'ing to the target user, and executing `osh.pl` again under their name

BreizhHardware commented

2026-05-07 00:17:30 +02:00

Author

Owner

@speed47 commented on GitHub (Nov 23, 2020):

Took the opportunity to add some smartness to adminSudo's autocompletion rules!

@speed47 commented on GitHub (Nov 23, 2020): Took the opportunity to add some smartness to adminSudo's autocompletion rules!

BreizhHardware commented

2026-05-07 00:17:30 +02:00

Author

Owner

@dwydler commented on GitHub (Nov 23, 2020):

Thanks a lot for the clarification.

@dwydler commented on GitHub (Nov 23, 2020): Thanks a lot for the clarification.

BreizhHardware referenced this issue

2026-05-07 00:19:39 +02:00

[PR #16] [MERGED] Upgrade fake-ttyrec version #171