CUT-2378: -Attribues Object needs custom type

[gweinjc]

Issues

• CUT-2378 - -Attribues Object needs custom type

What does this solve?

Through some discovery it was determined that the -Attributes object is being flattened by the SDKs and does not necessarily need a custom type.

As an example the following script would set sudo to enabled and withoutPassword to false

$attributes = [JumpCloud.SDK.V2.Models.IGraphOperationSystemAttributes]@{ 'sudo' = @{'enabled' = $true; 'withoutPassword' = $false } }
Set-JcSdkSystemAssociation -SystemId 61982961719e942987898f39 -id 5ef5fe69a899bd46963ab24a -op 'update' -type 'user' -Attributes $attributes

We can achieve the same result by doing the following:

Set-JcSdkSystemAssociation -SystemId 61982961719e942987898f39 -id 5ef5fe69a899bd46963ab24a -op 'update' -type 'user' -Attributes @{ 'sudoEnabled' = $true; 'SudoWithoutPassword' = $true }

This is due to the SDKs doing a sort of flattening to the sudo object and allowing us to instead call the sudoEnabled or SudoWithoutPassword property to set those values.

Rather than creating a custom object, we can update the documentation for this functionality

This behavior can also be applied to the Set-JcSdkUserAssociation function

Is there anything particularly tricky?

N/A

How should this be tested?

Pull the branch and import the updated version of the V2 SDK
Attempt to run the following script and ensure that the results are updated in the console:

Set-JcSdkSystemAssociation -SystemId <SystemID> -id <UserID> -op 'update' -type 'user' -Attributes @{ 'sudoEnabled' = $true; 'SudoWithoutPassword' = $true }

[jworkmanjc]

I think everything looks fine to me, Just two suggestions on the examples, if you remove associations from on object you technically don't need to pass in an attributes object. I think we should mark our examples this way but open for debate

[jworkmanjc]

Thanks for the examples!

[kmaranionjc]

Tests worked and code looks good. Great work