SA-3640-Get-JCassociation-Type-Bug-Fix #535
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
|
Thank you for the work on this! Confirming the issue in 2.7.0: And working now in this branch:
|
gweinjc
previously approved these changes
Oct 17, 2023
jworkmanjc
added
manual
jworkmanjc
approved these changes
Oct 18, 2023
kmaranionjc
temporarily deployed
to
PublishToPSGallery
GitHub Actions
Inactive
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.
Issues
What does this solve?
This change fixes issue where a device associated to a command gives error due to duplicate keys in the hash. Another issue is when a dynamic parameter -type is set, it does not get the right targetType.
Is there anything particularly tricky?
N/A
How should this be tested?
Get-JCAssociation -id YOURSYSTEMand a system bound to a commandGet-JCAssociation -id YOURSYSTEM -type system. Both commands should return an error