Add support for `environment` keyword in bridges
Summary
We need to support the environment
keyword in trigger jobs, and make sure that the environment variable is passed down to the child pipeline.
Steps to reproduce
From the code in the example:
stages:
- deploy
deploystacks:
stage: deploy
trigger:
include: path/to/child-pipeline.yml
parallel:
matrix:
- PROVIDER: aws
STACK: [monitoring, app1]
environment: $PROVIDER/$STACK
What is the current bug behavior?
The editor show LINT error. This GitLab CI configuration is invalid: jobs:deploystacks config contains unknown keys: environment.
Possible fixes
Support the environment
keyword in a trigger job.
Edited by Laura Montemayor