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

ISSUE_TEMPLATE: Add a note that sensitive information can be obfuscated #1092

Closed
johlju opened this issue Mar 17, 2018 · 0 comments · Fixed by #1093
Closed

ISSUE_TEMPLATE: Add a note that sensitive information can be obfuscated #1092

johlju opened this issue Mar 17, 2018 · 0 comments · Fixed by #1093
Labels
enhancement The issue is an enhancement request.

Comments

@johlju
Copy link
Member

johlju commented Mar 17, 2018

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

In the issue template, there is not a mention about that sensetive information can (and should) be obfuscated. For example when posting the configuration.

The DSC configuration that is using the resource (as detailed as possible)

n/a

Version of the operating system and PowerShell the target node is running

n/a

SQL Server edition and version the target node is running

n/a

What SQL Server PowerShell modules, and which version, are present on the target node.

n/a

Version of the DSC module you're using, or write 'dev' if you're using current dev branch

Dev

@johlju johlju added enhancement The issue is an enhancement request. in progress The issue is being actively worked on by someone. labels Mar 17, 2018
johlju added a commit that referenced this issue Mar 17, 2018
- Changes to SqlServerDsc
  - Updated ISSUE_TEMPLATE.md with a note about sensitive information (issue #1092).
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Apr 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant