Provide user/password to curl when called by clevis #401
Labels
Comments
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
Jan 31, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
|
Please, elaborate more on the use cases for this. How do you intend to use this? |
|
The idea is to have the possibility for Clevis to bind to those systems where there is a previous layer that requires using a user and a password. This is the case in RedHat ConsoleDOT, where you have tang, as a container, but access to this container requires binding to an external Route that requires user and password. |
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
May 3, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
May 3, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
May 3, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
May 9, 2023
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
sarroutbi
added a commit
to sarroutbi/clevis
that referenced
this issue
May 28, 2024
Resolves: latchset#401 Signed-off-by: Sergio Arroutbi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using tang pin, it would be desirable to have the possibility to provide user and password when calling "curl" from clevis.
IMHO, the recommended way would be to have a "netrc" file that is provided to curl, as if this file does not exist or fail to be read, curl continues execution and will continue as it is working currently
The text was updated successfully, but these errors were encountered: