Fix pipeline inputs finder when no config

Furkan Ayhanrequested to merge
534111-inputs-fetching-when-no-ci-config into master

What does this MR do and why?

Fix pipeline inputs finder when no config

Instead of returning an error when CI config is not found, we return a success response with empty inputs.

The project config may not exist if the project is using a policy. And we currently don't support inputs for policies.

References

Related to #534111 (closed)

Screenshots or screen recordings

Before After
Screenshot_2025-04-04_at_15.32.59 Screenshot_2025-04-04_at_15.33.09

How to set up and validate locally

  1. Enable the FF ci_inputs_for_pipelines.
  2. Create a PEP.
  3. Create a project using this policy.
  4. The project can't have a .gitlab-ci.yml file.
  5. The project must "autodevops" disabled.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports