Update oemetadata v2 integration in meta builder #1930
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the discussion
The oemetadata v2 is now close to be production ready, with release v2.1.0 staged for next week. This raises the need to update the metaBuilder to kick off the general upgrade of the oemetadata integration into the OEP. The general integration upgrade will take more time and includes updating OMI and migrating all existing metadata on the OEP to v2.
Type of change (CHANGELOG.md)
Changes
Documentation updates
Workflow checklist
Automation
Closes #1929
PR-Assignee
Reviewer