You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we've added runtime conditions to the stctl command for use during execution from Cloud Build. Instead, we want a runtime environment that interprets conditional directives like --execute_in_project=<foo> before calling exec on the remaining parameters passed to the docker image.
I imagine a new command cbenv or cbexec or cbopt or cbcond or similar, that accepts parameters from the environment and then execs the rest of argv if the conditions for execution are satisfied.
The first condition it should support is "EXECUTE_IN_PROJECTS=". With this directive it will be possible to have a single cloud build config with commands that should only be run in specific projects.
Currently, we've added runtime conditions to the stctl command for use during execution from Cloud Build. Instead, we want a runtime environment that interprets conditional directives like
--execute_in_project=<foo>
before callingexec
on the remaining parameters passed to the docker image.I imagine a new command
cbenv
orcbexec
orcbopt
orcbcond
or similar, that accepts parameters from the environment and then execs the rest of argv if the conditions for execution are satisfied.The first condition it should support is "EXECUTE_IN_PROJECTS=". With this directive it will be possible to have a single cloud build config with commands that should only be run in specific projects.
Additional ideas include conditional action on built-in environment variables -- https://cloud.google.com/cloud-build/docs/configuring-builds/substitute-variable-values For example,
IF_TAG_SET
, orIF_TAG_MATCHES=<pattern>
.The text was updated successfully, but these errors were encountered: