Conversation
…hema: Can do both for listing all in schema & listing for single table
This file contains hidden or 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
HotFeature (->master) which is needed for energy the databus <-> oep integration.
First, we wanted to integrate by adding a databus module to the OEP. As we reviewed this approach we came to the conclusion that an PULL approach would also be an option which also has the benefit that it deprecates the need for another module in the OEP and moves it to the Databus itself which will then harvest from the OEP-API.
In the future, we should define a best-practice way to harvest data from the OEP.
Type of change (CHANGELOG.md)
Features
Documentation updates
Workflow checklist
Automation
Closes #
PR-Assignee
Reviewer