search

modxevil / google-cloud-sdk

Automatically exported from code.google.com/p/google-cloud-sdk
0 stars 0 forks source link

error parsing app.yaml due to bad repository URI: git@github.com:SomeCompany/somecompany.git #442

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. use ssh git repo URI when git clone project source files:
    git clone git@github.com:SomeCompany/somecompany.git
2. stage the build:
    appcfg.sh stage build/exploded build/exploded/yamls
3. gcloud preview app deploy build/exploded/yamls/app.yaml

What is the expected output? What do you see instead?
ERROR: (gcloud.preview.app.deploy) An error occurred while parsing file: 
[/some/path/build/exploded/yamls/app.yaml]
Bad repository URI: git@github.com:SomeCompany/somecompany.git
  in "/some/path/build/exploded/yamls/app.yaml", line 48, column 1

What is the output of 'gcloud info'?

Google Cloud SDK [90.0.0]

Platform: [Mac OS X, x86_64]
Python Version: [2.7.10 (default, Jul 14 2015, 19:46:27)  [GCC 4.2.1 Compatible 
Apple LLVM 6.0 (clang-600.0.39)]]
Python Location: [/usr/bin/python]
Site Packages: [Disabled]

Installation Root: 
[/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk]
Installed Components:
  core: [2015.12.07]
  app-engine-python: [1.9.30]
  core-nix: [2015.11.24]
  app-engine-java: [1.9.30]
  gcloud: []
  gsutil-nix: [4.15]
  gsutil: [4.16]
  bq: [2.0.18]
  alpha: [2015.10.08]
  bq-nix: [2.0.18]

… private info …

Please provide any additional information below.

This is for app engine project running in managed vm mode.

Original issue reported on code.google.com by shouguo...@snapchat.com on 22 Dec 2015 at 12:03

GoogleCodeExporter commented 8 years ago 
We recently added support for propagating more types of source repository 
information through to the Cloud Debugger, and it looks like we missed some bad 
interactions between that work and some beta support for specifying source 
information in yaml files.

I'm working on a fix, but it will be at least a few weeks before it becomes 
publicly available. Meanwhile, you have a couple of options for a workaround.

Your best workaround from a functionality standpoint would be to link your 
github repo to a Google Cloud Repository (see 
https://cloud.google.com/tools/cloud-repositories/docs/cloud-repositories-hosted
-repository for information on how to do that). That will give our tools the 
ability to display your sources.

Alternatively, you can also work around the problem by removing the offending 
line from the generated app.yaml file after running the "stage", command but 
before deploying it. It's a bit of a pain to script it, but that should work.

Original comment by danie...@google.com on 21 Jan 2016 at 11:08

GoogleCodeExporter commented 8 years ago 
I believe the fix will be available in the next SDK release (which should come 
out very soon). Please follow up if that your issue is not addressed in the 
next update.

Original comment by danie...@google.com on 22 Jan 2016 at 6:52