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 option description for most session login options like (SSC) URL, user, password and token includes a list of environment variables that can be used to specify a default value for those options. This looks fine in help output and man-pages, but doesn't look very good in interactive prompts. For example:
> fcli ssc token create CIToken --url http://localhost:2220/ssc -ussc -p
Enter value for --password (SSC password. Environment variables:
FCLI_DEFAULT_SSC_PASSWORD: Shared with SC SAST/DAST
FCLI_DEFAULT_SSC_SESSION_PASSWORD: Only SSC session commands):
According to picocli documentation, the first line of the option description (as specified through numbered resource bundle keys) is used for interactive prompts. Resource bundles need to be updated to improve the output for interactive prompts, for example as follows:
password.0 = SSC password
password.1 = Environment variables:%n ${fcli.env.default.prefix}_SSC_PASSWORD: Shared with SC SAST/DAST%n ${fcli.env.default.prefix}_SSC_SESSION_PASSWORD: Only SSC session commands
The text was updated successfully, but these errors were encountered:
rsenden
changed the title
Improve interactive password prompts
Improve interactive password/token prompts
Jan 3, 2023
The option description for most session login options like (SSC) URL, user, password and token includes a list of environment variables that can be used to specify a default value for those options. This looks fine in help output and man-pages, but doesn't look very good in interactive prompts. For example:
According to picocli documentation, the first line of the option description (as specified through numbered resource bundle keys) is used for interactive prompts. Resource bundles need to be updated to improve the output for interactive prompts, for example as follows:
The text was updated successfully, but these errors were encountered: