Figure out a way to proactively update configs using deprecated features #159
Assignees
Comments
|
ping the sync |
lbarcziova
added a commit
to lbarcziova/research
that referenced
this issue
Apr 12, 2023
The script provides 3 commands (see particular command's --help for more info): 1. download-configs - to download the configs of the repos that used Packit Service in the past year 2. list-affected - to list the projects affected by particular migration 3. migrate - to update the config and create PR Related to packit#159 Related to packit/packit-service#1775
lbarcziova
added a commit
to lbarcziova/research
that referenced
this issue
Apr 20, 2023
The script provides 3 commands (see particular command's --help for more info): 1. download-configs - to download the configs of the repos that used Packit Service in the past year 2. list-affected - to list the projects affected by particular migration 3. migrate - to update the config and create PR Related to packit#159 Related to packit/packit-service#1775
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In many cases transforming deprecated config options (like
synced_filesormetadata) into the current format can be done programmatically, so we could come up with a way to propose these updates as PRs to the projects still using them. This could speed up their deprecation and let us remove some code sooner.Research how this could be done.
One of the things that needs to be done is to get an up-to-date version of all the packit.yaml-s currently in use. We discussed either saving them in the DB, or writing a script to get the list of projects and branches using the service API, and downloading the configs.
The text was updated successfully, but these errors were encountered: