Dockerfile.rlserver: copy IoTDB runtime config file #22
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
Copy the runtime config file for connections to Apache IoTDB to the docker image. This is required when IoTDB is used as the VISSR data store backend. Signed-off-by: Stephen Lawrence <[email protected]>
|
@UlfBj @petervolvowinz apologies for the short notice but I would appreciate a quick yes/no on this PR if possible as its a change needed for the COVESA Central Data Service Playground and I wish to make a release before the AMM. If its no I need to make a decision to either document a manual file change or fork the Dockerfile. |
|
Thanks @petervolvowinz. Much appreciated |
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.
Copy the runtime config file for connections to Apache IoTDB to the docker image. This is required when IoTDB is used as the VISSR data store backend.
The config file in question is already (always) in the VISSR source tree so there is no danger of breaking docker image build when IoTDB is not in use.