### Problem to solve In order to modify a specific Auto DevOps job, users must pull down the entire template and modify the needed parts. This means missing out on updates done by GitLab to the template and maintenance overhead. ### Target audience - Delaney, Development Team Lead, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#delaney-development-team-lead - Sasha, Software Developer, https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#sasha-software-developer ### Further details Use cases: 1. As a user, I want to modify an Auto DevOps job without rewriting the entire job definition. Maybe just change the `only` conditions, overwrite the `script`, or add a `before_script`. ### Proposal TBD - a mechanism through which user can specify custom objects/conditions that will take precedence over those defined in Auto DevOps without the need to pull down the entire template. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references https://gitlab.com/gitlab-org/gitlab-ce/issues/47234#note_147629654