Add support for reading in device extension files for container create hcs document #1060
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 PR adds support for device extensions. A device extension is generally used as part of the assigned device code flow. A device extension can be used to specify custom symlinks, registry values, and more that should be created in a container on creation.
As an example, this may be needed for assigned device scenarios where a driver may expect additional devices that it creates itself in the container's device object namespace to function correctly.
Signed-off-by: Kathryn Baldauf [email protected]