You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The command team51 github:update-repository-secret never asks the user for the new value to be updated.
One of the reasons is that, for security reasons, it actually sets the name of a constant that exists on OpsOasis, however, it should also support inputting the secret directly in plaintext.
In the code, the only place where $secret_value is set is on line 92:
The command
team51 github:update-repository-secret
never asks the user for the new value to be updated.One of the reasons is that, for security reasons, it actually sets the name of a constant that exists on OpsOasis, however, it should also support inputting the secret directly in plaintext.
In the code, the only place where
$secret_value
is set is on line 92:We might want to make the
secret_name
argument an--option
that receives a value. But there are security concerns that need to be understood first.Slack conversation.
The text was updated successfully, but these errors were encountered: