I'm developing a dynamic pipeline and I just noticed that the input request is filtered, and it doesn't include any custom keys.
What are some good ways for the bitbucket-pipelines.yml file of a repository to communicate some settings, needs, and desires to the dynamic pipeline function?
At the moment, for the `script:` key I can look for a special keyword (DSL), and replace it with one or more commands (e.g to wait for a db and initialise it, but without copying those commands to every repository that needs the database in the pipeline). If I see the database keyword, then I can also inject a database service in the `definitions:services:`.
I could use special keywords in `script:` for other things too, like running `npm` stuff for frontend projects.
But if I wanted the repository to communicate to me that it wants to do a cartesian product between several PHP versions and several Laravel versions, how would I do that without typing all the combinations into different steps - even if I were to then use DSL to expand the command list?
At the most extreme, I'd like to have no entries under `pipelines:` and populate them with stuff that was declared by other means.
I guess, lacking any other options, I could have a special step with just DSL in it, and in my pipeline I interpret it, remove it, and add the actual steps.
