Command line argument processing broken in version 92.0.0

[GoogleCodeExporter]

What steps will reproduce the problem?

Execute: gcloud dns record-sets transaction -z <your-zone-name> start
replacing <your-zone-name> with a DNS zone from your project.

What is the expected output? What do you see instead?

You should get: Transaction started [transaction.yaml].
You get: ERROR: (gcloud.dns.record-sets.transaction) Invalid choice: 
'<your-zone-name>'.

What is the output of 'gcloud info'?

Google Cloud SDK [92.0.0]

Platform: [Mac OS X, x86_64]
Python Version: [2.7.10 (default, Oct 23 2015, 18:05:06)  [GCC 4.2.1 Compatible 
Apple LLVM 7.0.0 (clang-700.0.59.5)]]
Python Location: [/usr/bin/python]
Site Packages: [Disabled]

Installation Root: [/Users/gabriel/gcloud/google-cloud-sdk]
Installed Components:
  core: [2016.01.12]
  core-nix: [2015.11.24]
  kubectl: []
  gcloud: []
  gsutil-nix: [4.15]
  gsutil: [4.16]
  bq: [2.0.18]
  alpha: [2016.01.12]
  bq-nix: [2.0.18]
  kubectl-darwin-x86_64: [1.1.3]

Please provide any additional information below.

I only hit this issue so far using the command below but I guess it might be 
spread over other commands as well.

Original issue reported on code.google.com by gabipetr...@gmail.com on 20 Jan 2016 at 2:21

[GoogleCodeExporter]

For the record, you can work around by using:

    $ gcloud dns record-sets transaction start -z <your-zone-name>

(Note the order of the flag vs. the command.)

We'll look into why gcloud is exhibiting this behavior.

Original comment by z...@google.com on 20 Jan 2016 at 2:54

[GoogleCodeExporter]

I figured that out. Forgot to mention it. But thanks! I am migrating the 
scripts now. :P

Original comment by gabipetr...@gmail.com on 20 Jan 2016 at 2:57

[GoogleCodeExporter]

Thank you for this feedback. 

This is a breaking change that was introduced in 92.0.0. Here is the entry from 
the release notes:

*   Changed behavior of the `--zone`/`-z` flag in the `gcloud dns record-sets`
    command group. This flag can no longer precede the command. For instance,
    `gcloud dns record-sets -z=mz list` will not work, but
    `gcloud dns record-sets list -z=mz` will.

Sorry about any inconvenience this caused you. The change was necessary to make 
the dns surface consistent with other surfaces.

Original comment by vil...@google.com on 20 Jan 2016 at 9:11

• Changed state: WorkingAsIntended

[GoogleCodeExporter]

Original comment by vil...@google.com on 20 Jan 2016 at 9:17

• Added labels: Type-Other
• Removed labels: Type-Defect