Description of problem:

The --force flag for content-override commands now requires an input rather than acting as a flag where no --force means force=false and --force included means force=true.

It's possible some library was updated which changed this functionality.

How reproducible:

Unsure, only seen in tests.

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

Take a look at https://ci.theforeman.org/job/hammer-cli-katello-main-source-release/

Likely try running hammer activation-key content-override --force.

Actual behavior:
Force argument requires a boolean value.

Expected behavior:
Force argument requires no value.

Business Impact / Additional info:

This bug is going to make it into Hammer 1.18 which is shipping with Katello 4.18. Katello 4.18 RC1 is being released as of the time of writing this issue, so it needs to be handled quickly if we don't want the bug to make it to Katello 4.18 GA.