-
Notifications
You must be signed in to change notification settings - Fork 117
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
Error when using secrets, ^,^ being added #552
Comments
Hi there - could you please provide the debug output for the complete GitHub Actions workflow run? The separator is working as intended, it's a gcloud feature for using a custom separator. What is the full error message? The current message is truncated, so I cannot see the full error. |
I myself use - id: 'deploy'
uses: 'google-github-actions/deploy-cloudrun@v2'
with:
service: ${{ vars.SERVICE_NAME }}
image: europe-docker.pkg.dev/project/repo/image@${{ needs.build.outputs.digest }}
env_vars: |
PROJECT_ID=${{ vars.PROJECT_ID }}
NAMESPACE=${{ vars.NAMESPACE }}
GCP_STORAGE_BUCKET_NAME=${{ vars.GCP_STORAGE_BUCKET_NAME }}
secrets: |
MONGO_URI=${{ vars.MONGO_SECRET_NAME }}
SOME_SERVICE_API_KEY=${{ vars.SOME_SERVICE_API_KEY_SECRET_NAME }} Those environment vars are just |
|
Debug output:
|
TL;DR
When using multiple secrets in the secrets input for google-github-actions/deploy-cloudrun, additional
^,^
characters appear unexpectedly, preventing successful deployment.Expected behavior
I expected the gcloud run deploy command to execute without unexpected characters and to deploy successfully, with each secret correctly assigned to its respective environment variable or volume path.
Observed behavior
The gcloud run deploy command failed to run correctly. Unexpected
^,^
characters were added in front of the first secret and between secrets, resulting in a failed deployment.Action YAML
Log output
Additional information
Same happens also if I provide secrets in one line (space separated)
The text was updated successfully, but these errors were encountered: