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

NOISSUE - Use log level error for VermeMQ docker #1162

Merged
merged 4 commits into from
May 5, 2020
Merged

NOISSUE - Use log level error for VermeMQ docker #1162

merged 4 commits into from
May 5, 2020

Conversation

manuio
Copy link
Contributor

@manuio manuio commented May 4, 2020

Signed-off-by: Manuel Imperiale [email protected]

@manuio manuio requested a review from a team as a code owner May 4, 2020 19:42
@codecov-io
Copy link

codecov-io commented May 4, 2020

Codecov Report

Merging #1162 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1162   +/-   ##
=======================================
  Coverage   74.25%   74.25%           
=======================================
  Files         102      102           
  Lines        6835     6835           
=======================================
  Hits         5075     5075           
  Misses       1409     1409           
  Partials      351      351           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2b4cf8a...093f442. Read the comment docs.

drasko
drasko previously approved these changes May 4, 2020
Copy link
Contributor

@drasko drasko left a comment

Choose a reason for hiding this comment

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

LGTM

Signed-off-by: Manuel Imperiale <[email protected]>
@@ -208,8 +208,8 @@ services:
container_name: mainflux-vernemq
restart: on-failure
environment:
DOCKER_VERNEMQ_ALLOW_ANONYMOUS: "on"
DOCKER_VERNEMQ_LOG__CONSOLE__LEVEL: error
DOCKER_VERNEMQ_ALLOW_ANONYMOUS: ${MF_DOCKER_VERNEMQ_ALLOW_ANONYMOUS}
Copy link
Contributor

Choose a reason for hiding this comment

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

Would ommiting "" here create problem? I guess not, just asking if this was tested?

Copy link
Contributor Author

@manuio manuio May 4, 2020

Choose a reason for hiding this comment

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

AFAIK for docker-compose it's the same. But I didn't deeply tested.

Copy link
Collaborator

Choose a reason for hiding this comment

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

This will never be off because Manflux doesn't use Broker authentication. IMHO no need for env var.

Copy link
Contributor

@drasko drasko left a comment

Choose a reason for hiding this comment

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

LGTM

@manuio manuio merged commit 16ac44f into absmach:master May 5, 2020
@manuio manuio deleted the vermemq branch May 5, 2020 14:44
manuio added a commit that referenced this pull request Oct 12, 2020
* NOISSUE - Use log level error for VermeMQ docker

Signed-off-by: Manuel Imperiale <[email protected]>

* Add vermemq ENVARS

Signed-off-by: Manuel Imperiale <[email protected]>

* Remove DOCKER_VERNEMQ_ALLOW_ANONYMOUS from docker-compose

Signed-off-by: Manuel Imperiale <[email protected]>

* Revert DOCKER_VERNEMQ_ALLOW_ANONYMOUS

Signed-off-by: Manuel Imperiale <[email protected]>
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.

6 participants