Conversation
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.
What problem is this PR solving?
Allow custom OH Metadata file source
Related JIRA tickets
SNT-619
Changes
OpenHexa metadata is now in a different datasets and file name has changed.
To not have to change the code in the future, this PR updates the defaults and allow custom value in OH workspace config for the metadata configuration.
How to test
Open the Admin Panel and set the config to be:
If you don't have a setup for Niger, you'll need to set it up, you can reach me for this.
Go to data layers and create a new one, use the open hexa data layer type.
Go through the steps and verify that it works.
Print screen / video
N/A
Notes
Things that the reviewers should know:
Doc
Tell us where the doc can be found (docs folder, wiki, in the code...).