You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I updated between two 0.93.0-SNAPSHOT versions and realized that I get a NPE during the execution of ConsulConfigMigration in the latest version. It is searching for a SP_PULSAR_URL entry in Consul and if it does not exists the backend terminates.
Adding a SP_PULSAR_URL entry to Consul is a quick hack.
Is this a bug or just a strange configuration in my test env ?
How to reproduce?
No response
Expected behavior
No response
Additional technical information
No response
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Hi @obermeier, good catch 👍
Do you know if your existing 0.93.0-SNAPSHOT version was a bit older (from a time before we added the Pulsar support)?
I submitted a PR to quick-fix this, but still need to test this with an older version.
Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
Backend
What happened?
Hi, I updated between two 0.93.0-SNAPSHOT versions and realized that I get a NPE during the execution of ConsulConfigMigration in the latest version. It is searching for a SP_PULSAR_URL entry in Consul and if it does not exists the backend terminates.
Adding a SP_PULSAR_URL entry to Consul is a quick hack.
Is this a bug or just a strange configuration in my test env ?
How to reproduce?
No response
Expected behavior
No response
Additional technical information
No response
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: