Description of problem:
While using Hammer we sometimes don't want the values in defaults to step in and it would be helpful to have a switch to disable the defaults
There is no way how to disable the defaults from applying
There is a switch such as:
hammer --no-defaults user list
Created redmine issue https://projects.theforeman.org/issues/25307 from this bug
Bryan, yes, it most probably will go to hammer 0.15.1 which will be in Foreman 1.20
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25307 has been resolved.
The fix for this one is already in the 6.5 SNAP.
Can you please provide following information
1. Significance and expected behaviour of no-default flag.
2. Does default here implies to default user or also to other default setting of hammer.
3. Exact steps to reproduce/verify this.
first of all I should have explained what I mean by the "defaults".
The defaults is a feature of Hammer CLI allowing user to set default values for certain CLI options. E.g. If I use only a single organization in Satellite i can do
hammer defaults add --param-name organization-id --param-value 1
and from now on hammer automatically adds --organization-id=1 to each command that has the option.
Sometimes this behavior is not wanted and --no-use-defaults will make hammer to ignore the set defaults. You can also turn off the defaults in cli config (permanent -no-use-defaults) in which case you may use --use-defaults on CLI to temporarily override and enable defaults.
Thanks for information I am able to verify this with snap 8.
Verified build: satellite-6.5.0 snap 8
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.