Can't deploy to a project ID that contains a domain name

[Sam]

I have a client that shared a projectID that he recently created so that I could deploy to it.

When I go to console/manage all projects, I see a list of all my project IDs, but his is the only one that contains a domain name.

example "domain.com:projectname-12345"

I've tried to deploy to just "projectname-12345" and also to "domain.com:projectname-12345" using goapp deploy and they both return

This application does not exist (app_id=u'domain.com:projectname-12345').

or

This application does not exist (app_id=u'projectname-12345').

What should I be putting in the application: line for app.yaml?

Thanks

[Nicholas (Google Cloud Support)]

Project IDs may include domains. If so, the domains are present in the ID in just the way you describe 'domain.com:project-id'. An example can be seen in this Identifying projects article.

I tested a few different scenarios of visibility and permissions.

Using appcfg.py (goapp is essentially a wrapper for this):

• With a existing project and the developer using appcfg.py not added with any role, I received a permissions error when attempting to deploy. 
  
• With a existing project and the developer using appcfg.py added as a viewer, I received the same permissions error as above.
  
• With a non-existing project, I received the error you described.
  

Using gcloud preview app deploy, I received a few different types of permission errors with the examples listed above but never a non-existent error.

Assuming you've correctly tested both possible IDs, you've confirmed having development/deployment permissions with the affect project, that you've updated and tested both appcfg.py and gcloud, I would suggest that you PM me the following information so that I may investigate this further in the event that this is a very unique error:

• The domain under which this project was creating
  
• The project ID (not project name) with which this project was created
  
• The account from which you are attempting to deploy the application
  

Though the above are not solutions, I hope they at least clarify some things.

[Nicholas (Google Cloud Support)]

Thank you for reaching out in private and providing the information I requested.

I've confirmed that the project you were attempting to deploy to was in fact a domain-scoped project like domain.com:project-id. I also confirmed that your personal account was added as an owner to said project. You've mentioned that the the project owner has since created a non-domain-scoped project thereby eliminating this permissions issue.

I would like to confirm however following the Configuring permissions on Google Cloud Platform article about team members if you could be added as a user to the domain by the domain administrator and try deployment from that account. I ask because the following statement seems to imply that a Apps Domain account must be used to deploy an application:

If you are using a Google Apps domain, the administrator for your domain should first create the Google account from within the Users panel of your Admin Console.

I hope this helps.

On Wednesday, February 24, 2016 at 7:33:39 PM UTC-5, Sam wrote: