Skip to content

Conversation

@ashvindeodhar
Copy link
Member

CNM starts by default when CNS starts. This change prevents CNM
from starting by default. stopcnm commandline option can be used
to start CNM if needed.

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

@codecov
Copy link

codecov bot commented Jul 24, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #381   +/-   ##
=======================================
  Coverage   40.01%   40.01%           
=======================================
  Files          25       25           
  Lines        3546     3546           
=======================================
  Hits         1419     1419           
  Misses       1927     1927           
  Partials      200      200

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 2c7dc77...72dfc74. Read the comment docs.

Copy link
Member

@tamilmani1989 tamilmani1989 left a comment

Choose a reason for hiding this comment

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

@ashvindeodhar can you change the name of variable to startcnm and flip false/true flag? Otherwise it will be confusing. If they want to start cnm as part of cns, they can specify startcnm in command line.

ninzavivek
ninzavivek previously approved these changes Jul 24, 2019
@ashvindeodhar
Copy link
Member Author

@tamilmani1989 addressed your review comment.

@ashvindeodhar ashvindeodhar merged commit c7c3dd9 into Azure:master Jul 25, 2019
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.

3 participants