-
Notifications
You must be signed in to change notification settings - Fork 249
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
migrate: support migration of FBC to latest preferred FBC (#1144)
* remove defunct ref-style olm.bundle.object This commit removes a feature of FBC that has never actually been used in practice: the ability to reference a file in an olm.bundle.object property, where the path is relative to the directory in which the file containing the olm.bundle.object property exists. This was originally intended to be a way to avoid bloating the FBC, but it's presence has caused two problems: 1. It hinted that it would be okay for third-party properties and schemas to reference files in a similar way. 2. Because of (1), we have never really been able to make assumptions that would enable us to migrate and re-write FBC in a different hierarchy, which has been limiting. In short, it imposes a burden on catalog maintainers to keep a catalog in a filesystem structure that is imposed by the author of the catalog contribution. In practice, ref-style olm.bundle.object properties have never been used (as far as I'm aware), because no tooling has ever produced that style, and no one I have heard of is using other methods to render bundles into an FBC. Lastly, with the recent addition of the `olm.csv.metadata` property, the useful life of the `olm.bundle.object` property (which has always been alpha) is nearing an end. Signed-off-by: Joe Lanford <[email protected]> * migrate: support migration of FBC to latest preferred FBC This commit adds support for migrating FBC to the latest preferred FBC contents. Note that sqlite and bundle inputs are always rendered using the latest preferred FBC contents. The migrate command is updated to now support FBC images and directories as input (only sqlite was supported prior), such that the written output will always be migrated. The render command is updated with a `--migrate` flag that allows a caller to opt into migration during rendering. Under the hood, both of these subcommands use the action.Render struct, which has a new `Migrate` boolean field that callers can use to enable/disable the migration behavior. Signed-off-by: Joe Lanford <[email protected]> --------- Signed-off-by: Joe Lanford <[email protected]>
- Loading branch information
1 parent
eaebcf6
commit 5e3fa99
Showing
15 changed files
with
464 additions
and
300 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.