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
{{ message }}
This repository has been archived by the owner on Jun 25, 2024. It is now read-only.
Thank you for this great plugin. We have a use case where we are using this plugin to trigger downstream pipelines, however, we also need one or some of the downstream pipelines to use another plugin, for example to retrieve secrets from AWS secrets manager.
At first, we worked around it by having the aws plugin listed before the monorepo-diff plugin, store the secret in an environment variable that can then be passed to monorepo-diff, which in turn would use it in downstream pipelines. The following works, however, it exposes the retrieved secrets into buildkite runner's environment tab in the pipeline job since monorepo-diff is creating the job with an environment variable.
I tested a quick fix and this does seem to do the trick and keep the secrets from being exposed. I'm happy to provide the contributing PR to add this
The text was updated successfully, but these errors were encountered:
jortega0
changed the title
Cannot define pipelines with plugins without exposing secrets
Cannot define downstream pipelines with multiple different plugins
Oct 12, 2023
Hello folks,
Thank you for this great plugin. We have a use case where we are using this plugin to trigger downstream pipelines, however, we also need one or some of the downstream pipelines to use another plugin, for example to retrieve secrets from AWS secrets manager.
At first, we worked around it by having the aws plugin listed before the monorepo-diff plugin, store the secret in an environment variable that can then be passed to
monorepo-diff
, which in turn would use it in downstream pipelines. The following works, however, it exposes the retrieved secrets into buildkite runner'senvironment
tab in the pipeline job sincemonorepo-diff
is creating the job with an environment variable.Therefore we need a feature that can allow for being able to specify plugins per each of the downstream jobs, something like this:
I tested a quick fix and this does seem to do the trick and keep the secrets from being exposed. I'm happy to provide the contributing PR to add this
The text was updated successfully, but these errors were encountered: