config-ssh overrides the previous config when used with a different project

[GoogleCodeExporter]

When "glcoud compute config-ssh" was used with a project A, the configuration 
is overridden when we call it again with another project.

For instance:
"gcloud compute config-ssh --project B" will override the configuration 
generated by the previous command "gcloud compute config-ssh --project A" 
instead of merging all the Google Compute entries.

What is the output of 'gcloud info'?
amaury@lumapps:~$ gcloud info
Google Cloud SDK [95.0.0]

Platform: [Linux, x86_64]
Python Version: [2.7.11 (default, Jan 11 2016, 21:04:40)  [GCC 5.3.1 20160101]]
Python Location: [/usr/bin/python2]
Site Packages: [Disabled]

Installation Root: [/home/amaury/.local/google-cloud-sdk]
Installed Components:
  kubectl: []
  app-engine-python: [1.9.31]
  core-nix: [2015.11.24]
  core: [2016.01.29]
  app-engine-java: [1.9.31]
  gcloud: []
  gsutil-nix: [4.15]
  app-engine-python-extras: [1.9.21]
  gsutil: [4.16]
  bq: [2.0.18]
  kubectl-linux-x86_64: [1.1.4]
  bq-nix: [2.0.18]
System PATH: 
[/home/amaury/.local/google-cloud-sdk/bin:/home/amaury/.local/npm-packages/bin:/
home/amaury/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:
/sbin]
Cloud SDK on PATH: [True]

Installation Properties: [/home/amaury/.local/google-cloud-sdk/properties]
User Config Directory: [/home/amaury/.config/gcloud]
User Properties: [/home/amaury/.config/gcloud/properties]
Current Workspace: [None]
Workspace Config Directory: [None]
Workspace Properties: [None]

Account: [amaury@lumapps.com]
Project: [xxxxxx]

Current Properties:
  [core]
    project: [xxxxxx]
    account: [amaury@lumapps.com]
    disable_usage_reporting: [True]
  [app]
    suppress_change_warning: [true]

Logs Directory: [/home/amaury/.config/gcloud/logs]
Last Log File: [/home/amaury/.config/gcloud/logs/2016.02.08/14.14.53.026787.log]

Original issue reported on code.google.com by ama...@lumapps.com on 8 Feb 2016 at 1:27

[GoogleCodeExporter]

Thanks for reporting this issue. We've filed a feature request internally to 
handle this scenario more intelligently.

Please let us know if you're having trouble working around this.

Original comment by z...@google.com on 18 Feb 2016 at 6:57

[GoogleCodeExporter]

Original comment by z...@google.com on 18 Feb 2016 at 7:07

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by jsche...@google.com on 14 Mar 2016 at 8:36

• Added labels: log-27244024