You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After paketo-buildpacks/libpak#327 is implemented, there will be a large task required to update the metadata of dependencies. Some of this data exists but can be migrated automatically. This issue is to investigate options and see if something can be done to help with the migration efforts.
Possible Solution
Modify octo to look at buildpack.toml, check for the old fields. Then update the new fields with the translated data from the old fields. This would then automatically submit PRs that could be merged. The downside is that these PRs would not be complete as there is some information that will require to be manually added, and they still need to be manually reviewed.
Create a throw-away tool. The tool would be run locally. It would modify buildpack.toml and update everything that could be automatically updated. A maintainer would finish with manual modifications and manually submit a PR.
No tools. Just manually make the updates and submit the PR. This is a one time task, the effort of making the tool is less than what will be saved.
Motivation
Ease the migration of metadata.
The text was updated successfully, but these errors were encountered:
Describe the Enhancement
After paketo-buildpacks/libpak#327 is implemented, there will be a large task required to update the metadata of dependencies. Some of this data exists but can be migrated automatically. This issue is to investigate options and see if something can be done to help with the migration efforts.
Possible Solution
Modify
octo
to look atbuildpack.toml
, check for the old fields. Then update the new fields with the translated data from the old fields. This would then automatically submit PRs that could be merged. The downside is that these PRs would not be complete as there is some information that will require to be manually added, and they still need to be manually reviewed.Create a throw-away tool. The tool would be run locally. It would modify
buildpack.toml
and update everything that could be automatically updated. A maintainer would finish with manual modifications and manually submit a PR.No tools. Just manually make the updates and submit the PR. This is a one time task, the effort of making the tool is less than what will be saved.
Motivation
Ease the migration of metadata.
The text was updated successfully, but these errors were encountered: