-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GCP Deployment Manager is running yarn again (instead of using packaged file from Serverless) #263
Labels
Comments
Lusitaniae
changed the title
GCP deployments are running yarn again (instead of using packaged file from Serverless)
GCP Deployment Manager is running yarn again (instead of using packaged file from Serverless)
Jun 8, 2021
Including deployment tokens in package.json works around the problem, but it would be preferred not do it that way. |
Hello @Lusitaniae - I'm going to move this issue to Google plugin repository as it seems more fitting there. Also, please include reproducible steps and sample |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm deploying two functions from my CI/CD pipeline
One in AWS, one in GCP
Both of them are pulling repos from our private Gitlab besides all the other public dependencies from npm.
It seems that after serverless packages and uploads the packge to Google Cloud, GCP Deployment Manager is running Yarn again and failing at the yarn step because it's unable to authenticate to our private repos?
Is that expected?
I'd expect a consistent behavior with AWS deployments but GCP stands out?
The text was updated successfully, but these errors were encountered: