Automate Renovate Ticket Workflow
## Description
Working Renovate tickets requires many manual steps that increase the potential for errors and duration to work the ticket. Full automation of the process may not be possible, but sections could be improved or automated.
Goal: Renovate tickets take less than one day to be merged into both the package and umbrella repo.
Initial ideas:
- Linking the DEVELOPER_MAINTENANCE files to the Renovate ticket, rather than the developer having to pull it up
- Embedding the checklist in the ticket (pulling from DEVELOPER_MAINTENANCE)
- Dynamically tailored for each package
- Link the upstream release notes in the ticket
- Automatically checking for upstream Helm chart that matches the new image version
- Automatically move to `status::blocked` or `status::ready-to-work` as appropriate
- Automatically conducting the Helm chart diff and report
[Documentation For Renovate Dev Workflow](https://repo1.dso.mil/big-bang/pipeline-templates/renovate-runner/-/blob/main/BigBang.md?ref_type=heads#testing)
## Requirements/Scope
- [x] Technical approach
- [x] Research and document potential approaches in an ADR
- [x] Obtain approval of the ADR
- [x] Populate epic details and create issues based on ADR
## Out of Scope
Packages that are not Core or Add Ons
## Duration
6-8 weeks
## Team
The team responsible for completing the Epic, including any cross-functional or external teams.
## Epic Team Members
Matt Vasquez (Lead)
Alozie Obuh
Daniel Pritchett
## Dependencies
N/A
## Risks
Risks are low to none with given testing process.
## Acceptance Criteria
All child issues are completed.
## Related Issues and/or Epics
N/A
epic