Skip to content

Place DSCv3 resource manifests in the package #5433

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

Merged
merged 8 commits into from
May 6, 2025

Conversation

JohnMcPMS
Copy link
Member

@JohnMcPMS JohnMcPMS commented May 5, 2025

Change

Adds a method to write all manifests to a directory with one command. Uses that to write all DSCv3 resource manifests and add them to the package files.

Also changes the "module" name for the dev package to add ".Dev" and updated export to use the shared definition of the module name. This involved a minor refactor to remove static globals and unnecessary string constructions.

Finally, moves to using the DSC v3 UserSettingsFile resource rather than the v2 version.

Validation

The package builds successfully as desired locally.

Microsoft Reviewers: Open in CodeFlow

@JohnMcPMS JohnMcPMS requested a review from a team as a code owner May 5, 2025 20:35
yao-msft
yao-msft previously approved these changes May 5, 2025
{
Argument GetOutputFileArgument()
{
return { Execution::Args::Type::OutputFile, Resource::String::OutputFileArgumentDescription, ArgumentType::Standard };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Do we consider differentiating output file vs output directory?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed the description, left the arg type the same.

yao-msft
yao-msft previously approved these changes May 5, 2025
@JohnMcPMS JohnMcPMS merged commit 565344c into microsoft:master May 6, 2025
9 checks passed
@JohnMcPMS JohnMcPMS deleted the dsc-manifest-packaged branch May 6, 2025 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants