Open tthebst opened 4 years ago
Resolved.
Leaving open until the new version of the orb is published. Blocked by #7
@KyleTryon Will it be fixed soon? Thanks
I would like to set environment variables
as well via the /deploy
command, any updates when this might be fixed?
@KyleTryon any chance we can bump this up in priority? would love to use the official orb but we really need the args parameter
@mareksuscak -- An alternative I went with was using Github Actions, the port from CircleCI --> Github Actions was fairly easy 🚀
Environment Variables
are fully supported and Github now supports manual triggers
as well -- https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
That commit above didn't even work. Here's my workaround that did work: https://github.com/ternandsparrow/wild-orchid-watch-api-facade/blob/f9b0ad0/.circleci/config.yml#L54-L91.
This is still a problem in the latest published version. A solution is to write a custom command by copy pasting and modifying the body.
Any updates on this?
Any updates?
Orb Version 1.0.2
Describe the bug ENV variables passed in args don't get added to env variables in cloud run
To Reproduce
Expected behavior
Environment variables show up in cloud run yaml file.
Additional context
${aws_secret_access_key} is circleci environment variable. To reproduce can also passs specific value.