Bug #14333
closedhammer activation-key --unlimited-content-hosts flag is confusing
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1314775
Description of problem:
unlimited-hosts flag is not required by `hammer activation-key create` as there's no limit set by default if no --max-content-hosts is used.
the `hammer activation-key update` on the other hand uses `--unlimited-content-hosts` flag for changing the limit to `unlimited`. However, this flag requires a boolean value (true/false, yes/no, 1/0). So we can have an AK with unlimited content hosts and update it using `--unlimited-content-hosts true`. The other way around - setting it back to limited, requires `--max-content-hosts` no matter what:
```- hammer -u admin -p changeme activation-key update --unlimited-content-hosts false --id 78 --organization-id 3
Could not update the activation key:
Validation failed: Max content hosts cannot be nil
```
making the use of `hammer activation-key update --unlimited-content-hosts false` useless as the same effect is being done using `--max-content-hosts` option only.
I believe we can drop `--unlimited-content-hosts` option from `create` subcommand
and change the behaviour of the same option in `update` subcommand not to accept any bool valie (only check for falg presence).
Version-Release number of selected component (if applicable):
6.2.0
How reproducible:
always
Steps to Reproduce:
1. hammer activation-key create --unlimited-content-hosts --organization-id 1 --name foo
2. hammer activation-key create --organization-id 1 --name bar
3. compare the content host limit of both activation keys
- for the `update` subcommand:
4. create AK with no content host limit
5. hammer activation key update --organization-id 1 --id 70 --unlimited-content-hosts false
Actual results:
as described above
Expected results:
no `--unlimited-content-host` option `create` subcommand,
make the same flag in `update` subcommand not to require any boolean value (presence-based check only)
Additional info:
snap 2.1