This repository has been archived by the owner on Oct 28, 2022. It is now read-only.
Issue 576 - Update to make use of additional API query parameters #615
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
…et all security tags by retrieving all pages
|
@kums1234, VMware has approved your signed contributor license agreement. |
|
jenkins test this please |
|
Tests Successful |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This update only makes changes to Get-NSXSecurityTag function.
The old process is commented out.
The update uses the filterBy and filterValue query parameters to pick specific security tag by name or objectId.
It allows retreives all security tags by retrieving all pages in a loop by incrementing the startIndex query parameter.