Support parameterized logic with IP ranges.
Nathan Fish
Question Thomas Linderdahl on this? What type of rules do you want to base this on? Can you provide some examples of parameters you would like to see supported? Would existing pipeline values work (https://circleci.com/docs/pipeline-variables/#pipeline-values)?
Thomas Linderdahl
Nathan Fish I'm not extremely well versed in circleci so I'll try to explain the usecase and hopefully that answers your question.
We use a homebrew orb in our pipelines. In some of our pipelines we need circleci_ip_ranges enabled for a specific job and in other pipelines we don't. We'd like to set this as an input parameter in the pipeline config like below. Hope that helps.
version: 2.1
orbs:
myord: orb@1.0
workflows:
version: 2
my_workflow:
- myorb/jobname:
enableips: true
Nathan Fish
Thomas Linderdahl my thought is possible enabling this to support expression based evaluation (like our expression based contexts) so you can evaluate based on pipeline parameters as well. So it would add a bit more dynamic nature to the feature.