Skip to content

Separate Microsoft.DSC metadata into directives and executionInformation#1387

Draft
SteveL-MSFT wants to merge 5 commits intoPowerShell:mainfrom
SteveL-MSFT:remove-ms-metadata
Draft

Separate Microsoft.DSC metadata into directives and executionInformation#1387
SteveL-MSFT wants to merge 5 commits intoPowerShell:mainfrom
SteveL-MSFT:remove-ms-metadata

Conversation

@SteveL-MSFT
Copy link
Member

@SteveL-MSFT SteveL-MSFT commented Feb 11, 2026

PR Summary

Separate the existing Microsoft.DSC namespace in metadata to directives and executionInformation:

  • separate directives for the config doc and resources
    • config:
      • resourceDiscovery
      • securityContext
      • version (requirements form for version of DSC)
    • resource:
      • requireAdapter
      • securityContext (overrides the one defined for config is specified)
  • executionInformation (for both config and resource level as-appropriate)
    • duration
    • endDatetime
    • executionType
    • operation
    • restartRequired
    • securityContext
    • startDatetime
    • version (of DSC)
    • whatIf

To not make this a breaking change, all the current returned Microsoft.DSC metadata is still there, so duplicated into executionInformation. If config uses Microsoft.DSC metadata for directives, a warning message is emitted. If both metadata and directives is used and they conflict, then an error is returned.

Since resourceDiscovery and requireAdapter were adding in 3.2-preview, removing those from Microsoft.DSC is ot a breaking change.

PR Context

Fix #1369
Fix #1343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove Microsoft.DSC metadata namespace Add metadata to require version check of DSC

1 participant