-
Notifications
You must be signed in to change notification settings - Fork 29
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
Renamed field that specifies adapted type #482
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a test
8c95c84
to
64176ec
Compare
This is already greatly covered by existing tests. Every non-List PSAdapter (and other adapters) operation uses this code path. |
But we don't have an explicit test to verify the behavior otherwise it would have failed before this change |
64176ec
to
55b152f
Compare
Added tests and a test adapter that verifies the renamed field. |
PR Summary
Previously, when an adapter process is invoked (for the
dsc resource ...
command) the actual resource type name is added to the input JSON bag as a specialtype
field.This results in collisions if resource has an actual
type
property. (e.g.PSDesiredStateConfiguration/File
resource)This PR renames the special field in the json to
adapted_dsc_type
which is less likely to cause collisions.