-
Notifications
You must be signed in to change notification settings - Fork 63
Version error when building web app (Cloud Shell) #15
Comments
Out of curiosity does your username start with admin_? If so, that would explain the issue since it has an underscore which is not permitted according to that error. If this is the case, we might be able to look into simplifying/stripping non-approved characters from usernames. |
Ah so I've tried it logged in on 2 accounts. admin@domain I assume admin is reserved by system so it changes it to admin_@cloudshell and it doesn't like . so changes that one to first_last@cloudshell |
I had the same issue, using the compute engine vm, as gcp account names are eric_white. Did the build as root without issue. |
I noticed this is still open, and I'm currently running into the same issue with the Is there a workaround other than running the build as |
So for what it's worth, this is defined here https://github.com/google/loaner/blob/master/loaner/deployments/deploy_impl.py#L272. @CoreyGriffin and others - to get around this, you can add the following flag to your deployment script --version="name". You'll replace name with your name or something that meets the criteria for the versioning. I.E. bash deployments/deploy.sh --version="testing" web prod. |
Thanks @helfrichmichael Kinda jank...but I ended up adjusting the logic in
|
Expected Behaviour
Running bash deployments/deploy.sh web prod would build and deploy application. Running it from CloudShell after configuring based on the wiki.
Actual Behaviour
ERROR: (gcloud.app.deploy) argument --version/-v: Bad value [admin_-20181002]: May only contain lowercase letters, digits, and hyphens. Must begin and end with a letter or digit. Must not exceed 63 characters.
Doesn't seem to like the following in deploy_impl.py
If you change to '--version=1' it works fine.
Steps to Reproduce
Build from Cloudshell?
The text was updated successfully, but these errors were encountered: