Skip to content
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

AzureDevOpsDsc: Make use of localization strings within the resources #21

Open
SphenicPaul opened this issue Jan 25, 2021 · 1 comment
Labels
Backlog - Mid Term Backlog - Mid Term enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.

Comments

@SphenicPaul
Copy link
Contributor

Details of the scenario you tried and the problem that is occurring

With other DSC Community modules (e.g. SqlServerDsc), the resources make use of the localization strings.

This module needs to make use of localisation strings as part of exceptions/errors and verbose output (also see #19).

@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. labels Jan 25, 2021
@SphenicPaul
Copy link
Contributor Author

Might need to consider where the localized strings, files would now have to sit in this class-based resource structure?

With the MOF-based resources, typically all DSC Resources had a subdirectory containing another en-US (and potential other) sub-directories containing:

  • about_<resourcename>.help.txt file
  • <resourcename>.strings.psd1 data file

Where will these files be located if there isn't a sub-directory for the resource?

@kilasuit kilasuit added the Backlog - Mid Term Backlog - Mid Term label Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog - Mid Term Backlog - Mid Term enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
Development

No branches or pull requests

3 participants