Open-ended authorization for includes
Problem to solve
https://gitlab.com/gitlab-org/gitlab-ce/issues/53903 introduces authorization support that uses the user's credential, but this could be expanded upon to allow open ended authorization and passing of user/password at runtime via secret variables.
This would primarily be for automation engineers responsible for managing includes. It will give them more flexibility to control how they are gathering included definitions.
This will also help companies that want to have includes be behind even further levels of security, where normal developers are not able to access them; perhaps in compliance or security workflows.
This could be implemented in the following form:
include: - remote: http://url.com user: user password: SECRET_VARIABLE - remote: http://url.com token: SECRET_TOKEN
What does success look like, and how can we measure that?
We can measure how many people are creating pipelines that use this syntax.