-
Notifications
You must be signed in to change notification settings - Fork 139
atomic stop errors out because opt* args are not there for stop #137
Comments
Fix issue with commands that don't have opt* args. Closes #137
Shouldn't be the 'optX' rather removed completely? The major problem is |
Yes makes sense to me. |
@bexelbie @baude @scollier @cgwalters WDYT? Does removing of this break anything? If a user used $OPT1 in atomic They would just need to do. OPT1="--debug" atomic install foobar Rather then atomic install --opt1="--debug" foobar |
@sub-mod this question is also for you... |
I think I can leave the commands in atomic, but just don't document them |
I unfortunately need optX to be present in atomic and in atomicapp LABELs to continue supporting deployment of nulecule apps via cockpit. |
THe current patch will still support --opt1 but it is no longer documented. Preferred method would be to execute OPT1="--option" atomic run foobar But atomic --opt1="--option" run foobar |
In the
cmd_env(self)
function the call to self.args.opt1 gives an error because stop doesn't have anopt1
arg.The text was updated successfully, but these errors were encountered: