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

Signal Stream type amqp does not work #90

Closed
jewel77 opened this issue Aug 21, 2018 · 2 comments
Closed

Signal Stream type amqp does not work #90

jewel77 opened this issue Aug 21, 2018 · 2 comments

Comments

@jewel77
Copy link

jewel77 commented Aug 21, 2018

Describe the bug
After running amqp-sensor.yaml, the sensor amqp-example is in Error phase with the message "the signal 'amqp' does not exist with the signal universe. please choose one from: [calendar resource nats webhook]"

To Reproduce
Steps to reproduce the behavior:

  1. Following Quick Start Guide to set up Argo Events and Argo,
  2. kubectl apply -f examples/amqp-sensor.yaml
  3. kubectl describe sensor.argoproj.io/amqp-example
  4. See "Phase: Error" and "Message: the signal 'amqp' does not exist with the signal universe. please choose one from: [calendar resource nats webhook]"

Expected behavior
Signal Guide says that amqp type is supported, and I see amqp is under signals/stream/builtin, but why the sensor with signal type amqp does not work.

@magaldima
Copy link
Contributor

This is a caveat of the current architecture. The quickstart guide has a note on step 3:

Note: In order to have a useful cluster for Argo Events, you will need to separately deploy the various signal services that you wish to support.

Ideally, built-in signals should not rely on additional components. This issue is currently being addressed in #92 .

@VaibhavPage
Copy link
Contributor

#92 is now merged

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

No branches or pull requests

3 participants