fix: c8y mapper config should use the value of c8y.mqtt as mqtt endpoint#3552
Merged
rina23q merged 1 commit intothin-edge:mainfrom Apr 10, 2025
Conversation
When C8yMapperConfig is constructed from tedge config, by mistake, the http endpoint was used as the mqtt endpoint. Signed-off-by: Rina Fujino <rina.fujino.23@gmail.com>
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
Contributor
Robot Results
|
crates/extensions/c8y_mapper_ext/src/operations/handlers/config_update.rs
Show resolved
Hide resolved
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.
Proposed changes
This PR fixes the issue in #3545 (comment).
C8yMapperConfigused the HTTP endpoint as its MQTT endpoint by mistake. This causes the issue highlighted by #3545.Unfortunately, the method
C8yMapperConfig::from_tedge_config()cannot be tested by unit tests or integration tests. This is the reason of why this bug was not detected easily, although we have good unit/integration test coverage for that. The logic of replacing with proxy url that we have is correctly addressing the difference of these endpoints.Types of changes
Paste Link to the issue
#3545
Checklist
just prepare-devonce)just formatas mentioned in CODING_GUIDELINESjust checkas mentioned in CODING_GUIDELINESFurther comments