Pre-filled values not working when specifying a remote CI/CD configuration file

Summary

One of our customers is pointing the CI/CD configuration file to a URL pointing to the GitLab instance itself, something like https://example.gitlab.com/jdasmarinas/common/-/raw/main/.gitlab-ci.yml to share the YAML files from one project to the other.

However, they noticed that pre-filled values is not working for them despite having the proper format.

I was also able to reproduce this on GitLab.com:

• https://gitlab.com/jdasmarinas/nfs-test

In this case, the CI/CD configuration file is pointed to https://gitlab.com/jdasmarinas/common/-/raw/main/.gitlab-ci.yml

Steps to reproduce

1. Change the CI/CD configuration file and point it to a remote file (with proper format for pre-filled values in CI/CD).
2. Try to run a pipeline manually
3. Pre-filled values not showing in the UI.

Example Project

https://gitlab.com/jdasmarinas/nfs-test

What is the current bug behavior?

Pre-filled environment values are not showing when trying to run the pipeline manually.

What is the expected correct behavior?

Pre-filled environment values should show properly.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes