Skip to content

Remove legacy fetching for CI components

Avielle Wolfe requested to merge 415855-remove-legacy-component-fetching into master

What does this MR do and why?

Originally, CI components could be defined anywhere in a resource repository. Now, we require them to be inside a templates directory. We supported the legacy fetching for a few milestones to give users time to upgrade, and now we are removing it.

Related to #415855 (closed)

Changelog: removed

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #415855 (closed)

Merge request reports