[ACR] The --admin-enabled boolean parameter requires a value when creating a registry

If I try running az acr create --admin-enabled, it complains about the --admin-enabled parameter needing a value. For boolean flags, which default to false, it would be nice if simply specifying them, without a value, was enough to indicate a true value.

Numerous other commands in the CLI provide this behavior (e.g. the --is-linux parameter of the az appservice plan create command), and so, consistency would be helpful for ease-of-use. Maybe this ACR behavior is the preferred way, and we should just correct other commands to be congruent. I’m cool either way, though I’d vote to not require explicitly adding true.

[tjprescott]

I definitely don’t recommend two flags. However, you can have a three state solution that works. @shhsu and I discussed the following: create

--admin-enabled  (True is implied)
--admin-enabled True (explicit)
--admin-enabled False (explicit)
(omitting is implicitly false)

update

--admin-enabled True (explicit)
--admin-enabled False (explicit)
(omitting means don't change)

In this way, you have consistency between create and update for those who value that, you have the ease of simply specifying a flag on create for those who value that, and you don’t have a breaking change.

[shhsu]

Ah, this should work action=‘store’, nargs=‘?’, const=True, default=None