Dynamically Populated CI Variable Options

Proposal

When manually starting a pipeline, providing options to variables is a useful feature. Expanding on that feature would be to allow those options to not be static but allow for obtaining values to display to the user from external sources. This could be obtained through an API/curl call and allow for parsing of the data after being returned.

Example flow:

• In repository A:
  • A pipeline creates an artifact with a version number.
  • The pipeline tags the repository with that version number.
• In repository B:
  • Another artifact is built with a version number.
  • The pipeline tags the repository with the version number.
• In repository C:
  • A pipeline is started with variables containing options
  • The options are the tags retrieved from Repository A and Repository B as the version numbers.
  • The pipeline uses those version numbers to deploy the artifacts.

This would allow for greater flexibility of using the options to obtain information from outside the repository where the pipeline is executed without manually updating the CI Yaml file.