Skip to content
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

feat(triggers): Add MQTT Trigger with secure connection options #498

Merged
merged 3 commits into from
Sep 28, 2020

Conversation

lenny-goodell
Copy link
Member

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

No MQTT trigger currently exists

Issue Number: #454

What is the new behavior?

Now have MQTT Trigger option with ability to connect securely using secrets from secret provider.

Does this PR introduce a breaking change?

  • Yes
  • No

Are there any new imports or modules? If so, what are they used for and why?

no

Are there any specific instructions or things that should be known prior to reviewing?

Other information

@cloudxxx8
Copy link
Member

@judehung @FelixTing please help take a look

@lenny-goodell lenny-goodell force-pushed the mqtt-trigger branch 2 times, most recently from fe8e5be to cf4213e Compare September 22, 2020 16:27
@lenny-goodell lenny-goodell force-pushed the mqtt-trigger branch 5 times, most recently from 5885ac0 to f1c5bfe Compare September 22, 2020 17:29
@lenny-goodell
Copy link
Member Author

recheck

Copy link
Member

@jpwhitemn jpwhitemn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - looks like we settled on "mqtt-external" as the key.

Bit surprised that the test key certificates and keys are not flagged by Github (I had that happen in the past), but it looks like they were there before and now.

@lenny-goodell
Copy link
Member Author

Bit surprised that the test key certificates and keys are not flagged by Github

Yes, I get an email each time I push, but since they are for testing and not real, figured no worries...

@lenny-goodell
Copy link
Member Author

looks like we settled on "mqtt-external" as the key.

Yes, but I went with external-mqtt , but still open to suggestions. ;-)

Copy link
Member

@judehung judehung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@FelixTing FelixTing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thanks @lenny-intel

BTW, I tried using this MQTT Trigger to connect to and subscribe to the Mosquitto MQTT broker and also the AWS IoT MQTT broker, and got good results with both.

Copy link
Contributor

@jim-wang-intel jim-wang-intel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lenny-goodell lenny-goodell merged commit f40e2be into edgexfoundry:master Sep 28, 2020
@lenny-goodell lenny-goodell deleted the mqtt-trigger branch September 28, 2020 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add MQTT Trigger
8 participants