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

Handle Siddhi applications being updated as a config map #64

Closed
pcnfernando opened this issue Jul 29, 2019 · 0 comments · Fixed by #66
Closed

Handle Siddhi applications being updated as a config map #64

pcnfernando opened this issue Jul 29, 2019 · 0 comments · Fixed by #66

Comments

@pcnfernando
Copy link
Contributor

Description:
When Siddhi application is configured as a config map in Siddhi custom resource, during an update to the config map, the update flow of the Siddhi operator will not be triggered since the Siddhi custom resource was not updated, but one of its specification reference was updated.

We need to explicitly handle this case where we have to listen to changes in the object reference being used in Siddhi CRD under

apps:
  configMap: <appName>

Related Issues:
#31
#42
#62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant