Problems associated with a custom CI/CD configuration path

Since a 9.4 we are able to define a custom path of for CI/CD configuration file in project settings.

I created this issue to gather problems that might stem from this feature, as discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/35233#note_35337855.

One problem that might hit us in the future is not being able to read a configuration file for some old SHA.

• Let's assume that we create a pipeline for a SHA committed in January.
• In February someone changes CI/CD configuration path.
• In Match we want to access CI/CD configuration again for the SHA.
• We can't do that because we don't know what was the name of CI/CD configuration file.

Should we store this information in a database when we create a new pipeline?

/cc @bikebilly @ayufan