mattcasters opened a new issue, #9256:
URL: https://github.com/apache/hop/issues/9256
### What would you like to happen?
I want to have metadata that is shared across the whole hop configuration,
referenced in `hop-config.json`.
The idea is to be able to reference project folders on VFS locations that go
beyond the ones in the standard configuration. For example, if you would want
to reference a project on an SMB server you should be able to have a project
home folder in the configuration like `my-smb://project-folder/` and it should
just work. Same for git VFS etc.
The same goes for things like variable resolvers that you might want to have
available before a project is even addressed.
An example would be using two pieces of shared metadata:
* a HashiCorp Vault variable resolver that authenticates using a Kubernetes
key.
* a git VFS metadata element with the required secrets stored in the vault,
named `git-project`
* a project home folder pointing to `git-project:///`
Since this sort of thing is useful for execution in a container I think it
makes sense to be able to configure the Hop configuration in the container with
either a String in variable `HOP_CONFIG_SHARED_METADATA` or with a file
`HOP_CONFIG_SHARED_METADATA_FILE`. After configuration the content of both
would be replacing a sharedMetadata element in `hop-config.json`.
The challenge then is to make sure that when we create Hop metadata instance
the shared metadata is loaded first as a `MemoryMetadataProvider`, probably in
`HopMetadataInstance`.
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Config, Component: Containers
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
