Skip to content

Add support for discovery extensions #760

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

SteveL-MSFT
Copy link
Member

@SteveL-MSFT SteveL-MSFT commented Apr 24, 2025

PR Summary

  • Add new subcommand to dsc to list extensions: dsc extension list
  • Add new ExtensionManifest which is similar but differs from ResourceManifest. Only discover capability currently supported.
  • Enhance existing discovery code to handle both resources and extensions. This includes pre-discoverying extensions when discovering resources since an extension may participate. This included a new enum to handle returning either resources or extensions.
  • Write extensions as table when used interactively
  • Rename existing functions to generalize for both resource and extension use, this also required making some private functions public

The output from a discovery extension must match:

{ "resourceManifestPath": "<absolute path>" }

PR Context

Fix #681

@SteveL-MSFT SteveL-MSFT force-pushed the discovery-extension branch 2 times, most recently from f720dd9 to 35daf35 Compare April 24, 2025 01:19
@SteveL-MSFT SteveL-MSFT force-pushed the discovery-extension branch from 83825d3 to a9277d8 Compare April 24, 2025 20:20
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.

Discovery extension type resource
1 participant