Add target node documentation #536
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nothing in the docs currently shows how pylxd can specify the target node on creation. The location can be read from the instance and is listed as an attribute, but specifying 'location' in the config on creation does not create the desired result.
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #536 +/- ##
=======================================
Coverage 97.43% 97.43%
=======================================
Files 56 56
Lines 4251 4251
=======================================
Hits 4142 4142
Misses 109 109 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
stgraber
approved these changes
Mar 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nothing in the docs currently shows how pylxd can specify the target node on creation. The location can be read from the instance and is listed as an attribute, but specifying 'location' in the config on creation does not create the desired result.