-
Notifications
You must be signed in to change notification settings - Fork 484
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor Core Command via MessageBus to use new MessageBus Request API #4309
Labels
enhancement
New feature or request
tech-debt
issue_type denoting refactoring to improve design or removal of temporary workarounds
Milestone
Comments
lenny-goodell
added
enhancement
New feature or request
tech-debt
issue_type denoting refactoring to improve design or removal of temporary workarounds
labels
Jan 25, 2023
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Jan 25, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Aslo the internal response topic is aways edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. coses edgexfoundry#4309 signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Jan 25, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Aslo the internal response topic is aways edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. coses edgexfoundry#4309 signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Jan 25, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 Signed-off-by: Leonard Goodell <[email protected]>
5 tasks
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Jan 31, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 Signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Jan 31, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 Signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Feb 6, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 Signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Feb 7, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 fixes #4304 Signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
to lenny-goodell/edgex-go
that referenced
this issue
Feb 7, 2023
…equst API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes edgexfoundry#4309 fixes #4304 Signed-off-by: Leonard Goodell <[email protected]>
lenny-goodell
pushed a commit
that referenced
this issue
Feb 7, 2023
…equest API (#4310) * refactor!: Rework Core Commands via messaging to use new MessageBus Request API BREAKING CHANGE: Topics configuration for Core Command has changed. Also the internal response topic is always edgex/response/<responding-service-name>/<request-id>. The prefix for this is now part of the standard MessageBus configuration. closes #4309 Signed-off-by: Leonard Goodell <[email protected]>
github-project-automation
bot
moved this from QA/Code Review
to Minnesota Done
in Technical WG
Feb 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
tech-debt
issue_type denoting refactoring to improve design or removal of temporary workarounds
🚀 Refactor Request
Relevant Package [REQUIRED]
This feature request is for Core CommandDescription [REQUIRED]
MessageBus now has the new Request API with encapsulates the request/response of the MessageBus. Core Commands via MessageBus needs to be refactored to use it.Describe the solution you'd like
Refactor Core Command via MessageBus to use new MessageBus Request APIDescribe alternatives you've considered
Have you considered any alternative solutions or workarounds?The text was updated successfully, but these errors were encountered: