If the user wants to configure the pulp config interactively, the header options does not accept an empty value. This results in an endless loop in the interactive CLI until the user passes any value such as :
pulp config create -i
Config file location [/home/mike/.config/pulp/cli.toml]:
API base url [https://localhost]: http://localhost:8080
Absolute API base path on server (not including 'api/v3/') [/pulp/]:
Domain to work in if feature is enabled [default]:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.:
Custom header to add to each api call. Name and value are colon separated. Can be specified multiple times.: :
[....]
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times:
Select pluins supposed to be loaded. Can be specified multiple times: :
Error: Profile cli:
'headers' must be a list of strings with a colon separator
'plugins' must be a list of strings
Summary
If the user wants to configure the pulp config interactively, the header options does not accept an empty value. This results in an endless loop in the interactive CLI until the user passes any value such as
:
Steps to reproduce
Expected behavior
If I pass a empty value during interactive CLI it should proceed to the next option and NOT crash.
The justified reason for this is because the CLI tool behaves correctly when the options for header & plugins are not passed as part of CLI command:
Stacktrace/Error log
Pulp and pulp-cli version info
Additonal context