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

Clarify which key is used for the Napalm port #145

Merged
merged 2 commits into from
May 21, 2018
Merged

Conversation

ogenstad
Copy link
Collaborator

The current docstring is wrong and can cause confusion.

Another solution would be to point to task.host.network_api_port but before we have a specific section in the documentation which talks about how these are connected I think it's better to point to the key as in this PR.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 674

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.871%

Totals Coverage Status
Change from base Build 670: 0.0%
Covered Lines: 951
Relevant Lines: 1024

💛 - Coveralls

@coveralls
Copy link

coveralls commented May 21, 2018

Pull Request Test Coverage Report for Build 676

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.871%

Totals Coverage Status
Change from base Build 670: 0.0%
Covered Lines: 951
Relevant Lines: 1024

💛 - Coveralls

@ogenstad
Copy link
Collaborator Author

Removed two extra ` characters to make pylama happy. Not sure if they are needed for anything?

@dbarrosop dbarrosop merged commit 962915a into develop May 21, 2018
@dbarrosop dbarrosop deleted the ogenstad_connection branch July 12, 2018 11:45
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