Sampler and Pester Test Updating

.gitattributes

@@ -0,0 +1,15 @@
+# Needed for publishing of examples, build worker defaults to core.autocrlf=input.
+* text eol=autocrlf
+
+*.mof   text eol=crlf
+*.sh    text eol=lf
+*.svg   eol=lf
+
+# Ensure any exe files are treated as binary
+*.exe binary
+*.jpg binary
+*.xl* binary
+*.pfx binary
+*.png binary
+*.dll binary
+*.so  binary

.github/ISSUE_TEMPLATE/General.md

@@ -0,0 +1,7 @@
+---
+name: General question or documentation update
+about: If you have a general question or documentation update suggestion around the resource module.
+---
+<!--
+    Your feedback and support is greatly appreciated, thanks for contributing!
+-->

.github/ISSUE_TEMPLATE/Problem_with_module.yml

@@ -0,0 +1,102 @@
+name: Problem with the module
+description: If you have a problem using this module, want to report a bug, or suggest an enhancement to this module.
+labels: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        TITLE: Please be descriptive not sensationalist.
+
+        Your feedback and support is greatly appreciated, thanks for contributing!
+
+        Please provide information regarding your issue under each section below.
+        **Write N/A in sections that do not apply, or if the information is not available.**
+  - type: textarea
+    id: description
+    attributes:
+      label: Problem description
+      description: Details of the scenario you tried and the problem that is occurring, or the enhancement you are suggesting.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Verbose logs
+      description: |
+        Verbose logs showing the problem. **NOTE! Sensitive information should be obfuscated.** _Will be automatically formatted as plain text._
+      placeholder: |
+        Paste verbose logs here
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: reproducible
+    attributes:
+      label: How to reproduce
+      description: Provide the steps to reproduce the problem.
+    validations:
+      required: true
+  - type: textarea
+    id: expectedBehavior
+    attributes:
+      label: Expected behavior
+      description: Describe what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: currentBehavior
+    attributes:
+      label: Current behavior
+      description: Describe what actually happens.
+    validations:
+      required: true
+  - type: textarea
+    id: suggestedSolution
+    attributes:
+      label: Suggested solution
+      description: Do you have any suggestions how to solve the issue?
+    validations:
+      required: true
+  - type: textarea
+    id: targetNodeOS
+    attributes:
+      label: Operating system you are running FabricTools on
+      description: |
+        Please provide as much as possible about the node running FabricTools. _Will be automatically formatted as plain text._
+
+        To help with this information:
+        - On a Linux distribution, please provide the distribution name, version, and release. The following command can help get this information: `cat /etc/*-release && cat /proc/version`
+        - On macOS, please provide the product version and build version. The following command can help get this information: `sw_vers`
+        - On a Windows OS please provide edition, version, build, and language. The following command can help get this information: `Get-ComputerInfo -Property @('OsName','OsOperatingSystemSKU','OSArchitecture','WindowsVersion','WindowsBuildLabEx','OsLanguage','OsMuiLanguages')`
+      placeholder: |
+        Add operating system information here
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: targetNodePS
+    attributes:
+      label: PowerShell version and build the target node is running
+      description: |
+        Please provide the version and build of PowerShell the target node is running. _Will be automatically formatted as plain text._
+
+        To help with this information, please run this command: `$PSVersionTable`
+      placeholder: |
+        Add PowerShell information here
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: moduleVersion
+    attributes:
+      label: Module version used
+      description: |
+        Please provide the version of the FabricTools module that was used. _Will be automatically formatted as plain text._
+
+        To help with this information, please run this command: `Get-Module -Name 'FabricTools' -ListAvailable | ft Name,Version,Path`
+      placeholder: |
+        Add module information here
+      render: text
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/Problem_with_resource.yml

@@ -0,0 +1,47 @@
+name: Problem with a function
+description: If you have a problem, bug, or enhancement with a function in this module.
+labels: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please prefix the issue title (above) with the function name, e.g. 'FunctionName: Short description of my issue'!
+
+        Your feedback and support is greatly appreciated, thanks for contributing!
+  - type: textarea
+    id: description
+    attributes:
+      label: Problem description
+      description: Details of the scenario you tried and the problem that is occurring.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Verbose logs
+      description: |
+        Verbose logs showing the problem. **NOTE! Sensitive information should be obfuscated.** _Will be automatically formatted as plain text._
+      placeholder: |
+        Paste verbose logs here
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: version
+    attributes:
+      label: Module Version
+      description: |
+        The version of the FabricTools module you are using. _Will be automatically formatted as plain text._
+        To help with this information, please run this command: `Get-Module -Name 'FabricTools' | ft Name,Version,Path`
+      placeholder: |
+        Paste output here
+    validations:
+      required: true
+  - type: textarea
+    id: suggestedSolution
+    attributes:
+      label: Suggested solution
+      description: Do you have any suggestions how to solve the issue?
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/Resource_proposal.yml

@@ -0,0 +1,43 @@
+name: New function proposal
+description: If you have a new function proposal that you think should be added to this module.
+title: "NewFunctionName: New resource proposal"
+labels: []
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please replace `NewFunctionName` in the issue title (above) with your proposed function name.
+
+        Thank you for contributing and making FabricTools better!
+  - type: textarea
+    id: description
+    attributes:
+      label: Function proposal
+      description: Provide information how this function will/should work and how it will help users.
+    validations:
+      required: true
+  - type: textarea
+    id: proposedProperties
+    attributes:
+      label: Proposed properties
+      description: |
+        List all the proposed properties and parameters that the function should have.
+      value: |
+        Parameter | Description | Data type | Default value | Allowed values
+        --- | --- | --- | --- | ---
+        ParameterName | Detailed description | String | None | Any
+
+        Property | Description
+        --- | ---
+        PropertyName | Detailed description
+    validations:
+      required: true
+  - type: textarea
+    id: considerations
+    attributes:
+      label: Special considerations or limitations
+      description: |
+        Provide any considerations or limitations you can think of that a contributor should take in account when coding the proposed function, and or what limitations a user will encounter or should consider when using the proposed function.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: "FabricTools Community"
+    url: https://github.com/dataplat/FabricTools/discussions
+    about: "To talk to the community and maintainers of FabricTools, please head to GitHub discussions."

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,63 @@
+# Pull Request
+
+<!--
+    Thanks for submitting a Pull Request (PR) to this project.
+    Your contribution to this project is greatly appreciated!
+
+    TITLE: Please be descriptive not sensationalist.
+    Prepend the title with the [DscResourceName] if your PR is specific to a DSC resource.
+    Also prepend with [BREAKING CHANGE] if relevant.
+    i.e. [BREAKING CHANGE][xFile] Add security descriptor property
+
+    You may remove this comment block, and the other comment blocks, but please
+    keep the headers and the task list.
+    Try to keep your PRs atomic: changes grouped in smallest batch affecting a single logical unit.
+-->
+
+## Pull Request (PR) description
+
+<!--
+    Replace this comment block with a description of your PR to provide context.
+    Please be describe the intent and link issue where the problem has been discussed.
+    try to link the issue that it fixes by providing the verb and ref: [fix|close #18]
+
+    After the description, please concisely list the changes as per keepachangelog.com
+    This **should** duplicate what you've updated in the changelog file.
+
+### Added
+- for new features [closes #15]
+### Changed
+- for changes in existing functionality.
+### Deprecated
+- for soon-to-be removed features.
+### Security
+- in case of vulnerabilities.
+### Fixed
+- for any bug fixes. [fix #52]
+### Removed
+- for now removed features.
+-->
+
+## Task list
+
+<!--
+    To aid community reviewers in reviewing and merging your PR, please take
+    the time to run through the below checklist and make sure your PR has
+    everything updated as required.
+
+    Change to [x] for each task in the task list that applies to your PR.
+    For those task that don't apply to you PR, leave those as is.
+-->
+
+- [ ] The PR represents a single logical change. i.e. Cosmetic updates should go in different PRs.
+- [ ] Added an entry under the Unreleased section of in the CHANGELOG.md as per [format](https://keepachangelog.com/en/1.0.0/).
+- [ ] Local clean build passes without issue or fail tests (`build.ps1 -ResolveDependency`).
+- [ ] Resource documentation added/updated in README.md.
+- [ ] Resource parameter descriptions added/updated in README.md, schema.mof
+      and comment-based help.
+- [ ] Comment-based help added/updated.
+- [ ] Localization strings added/updated in all localization files as appropriate.
+- [ ] Examples appropriately added/updated.
+- [ ] Unit tests added/updated. See [DSC Resource Testing Guidelines](https://github.com/PowerShell/DscResources/blob/master/TestsGuidelines.md).
+- [ ] Integration tests added/updated (where possible). See [DSC Resource Testing Guidelines](https://github.com/PowerShell/DscResources/blob/master/TestsGuidelines.md).
+- [ ] New/changed code adheres to [DSC Resource Style Guidelines](https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md) and [Best Practices](https://github.com/PowerShell/DscResources/blob/master/BestPractices.md).

.github/copilot-commit-message-instructions.md

@@ -0,0 +1,8 @@
+# Limit the subject line to 50 characters 
+Capitalize the subject/description line
+Do not end the subject line with a period
+Separate the subject from the body with a blank line
+Use the imperative mood in the subject line
+The subject line should be a single sentence with an action word and target with some reasoning add "for Pester Help Tests"
+Use the body to explain what and why in a friendly kind manner
+Say thank you at the end of the message