feat: specify the configuration path to use NRF version 1.6.0 #430
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
|
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
gatici
force-pushed
the
specify-configuration-files
branch
from
7cf0be1 to
775d28c
Compare
ghislainbourgeois
approved these changes
Dec 11, 2024
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.
Description
TLS paths and the configuration paths are parameterized in the Upstream with NRF version 1.6.0.
To use the Workload 1.6.0 and higher versions, this PR which specifies configuration and TLS file paths is required.
Warning: A new Rock version (1.6.0 or higher) should be used with this PR. Integration tests fails until we create a new Rock version and start to use it.Checklist: