[go: nahoru, domu]

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

Ensure that websocket (api, redis, ...) can be disable #5

Closed
manonviallet opened this issue Apr 17, 2019 · 1 comment
Closed

Ensure that websocket (api, redis, ...) can be disable #5

manonviallet opened this issue Apr 17, 2019 · 1 comment
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@manonviallet
Copy link
Contributor
manonviallet commented Apr 17, 2019

Problem to Solve

Ensure that websocket (api, redis, ...) can be disable with an option and all the application still works perfectly.

Current Workaround

None.

Proposed Solution

Implement an option in the configuration to be able to disable the "reactive" mode with Redis subscription.

Additional Information

None.

@SamuelHassine SamuelHassine changed the title Ensure that websocket (api, redis, ...) can be disable with an option and all the application still works perfectly Ensure that websocket (api, redis, ...) can be disable Apr 19, 2019
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Apr 20, 2019
@SamuelHassine
Copy link
Member

The option has been implemented "reactive": true|false in the configuration. Redis can now be disabled.

@SamuelHassine SamuelHassine added this to the 1.0-beta milestone Apr 20, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 20, 2019
@SamuelHassine SamuelHassine modified the milestones: v1.0.0-beta, v1.0.0 Jun 17, 2019
ParamConstructor referenced this issue in fbicyber/opencti__opencti Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

3 participants