feat: Support for import extension properties from other registry #78
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.
When creating a custom registry, it is inconvenient (and a potential source of error) to duplicate the data of those extensions that are also included in the registry maintained by Grafana. Support for importing extension data from other registries helps with this.
An optional origin registry URL can be specified with the
--origin
command line flag. If the extension is included in the origin registry, the default values of its properties will be the values specified in the origin registry. To import all the properties, it is enough to specify themodule
property. Properties in the origin registry can be overwritten in the registry source. For example, by specifying theversions
property, you can specify that only certain versions are included in the generated registry.