Merge pull request #16 from techthoughts2/Enhancements

Enhancements

Author: techthoughts2

.github/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Diag-V Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [3.0.2]
+
+- Removed unnecessary link from all help entries
+- Updated build process to latest standards (*no functional changes*)
+  - Updated gitignore
+  - Bumped install modules to latest versions
+  - Added GitHub community files (changelog/code of conduct / contributing / templates)
+  - Added vscode files
+  - Updated InvokeBuild file for project
+  - Separated public function tests from monolithic test file into separate test files
+- Updated link to tecthoughts site to have https instead of http
+
+## [3.0.1]
+
+- Fixed bug where Get-AllVHD was returning duplicated VHD results
+
+## [3.0.0]
+
+- Added Pester tests for all functions.
+- Re-wrote all functions from previous module versions to account for bugs and layout of new tests. Removed Write-Host - all functions now return PowerShell objects.
+- Fixed numerous bugs.
+- Added additional functionality to several functions. Some functions were renamed to more clearly indicate what they are now capable of.
+- Adjusted layout of Diag-V module to CI/CD standards.
+- Added code to support AWS Codebuild.
+- Added new icon.
+- Rewrote all documentation to capture new changes and capabilities.
+
+## [2.0]
+
+- Complete re-write from original script version.
+- Converted Diag-V from a ps1 PowerShell script to a fully supported PowerShell module.
+- Redesigned all diagnostic functions:
+- Improved error control, General bug fixes, Better readability, Added new Hyper-V log parser function.
+
+## [1.0]
+
+- Initial .ps1 script version of Diag-V.

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at tech@techthoughts.info. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq)

.github/CONTRIBUTING.md

@@ -0,0 +1,51 @@
+# Contributing
+
+Thanks for your interest in contributing to the **Diag-V Project**.
+
+Whether it's a bug report, new feature, correction, or additional documentation, your feedback and contributions are appreciated.
+
+Please read through this document before submitting any issues or pull requests to ensure all the necessary information is provided to effectively respond to your bug report or contribution.
+
+Please note there is a code of conduct, please follow it in all your interactions with the project.
+
+## Reporting Bugs/Feature Requests
+
+When filing an issue, please check [existing open](https://github.com/techthoughts2/Diag-V/issues), or [recently closed](https://github.com/techthoughts2/Diag-V/issues?q=is%3Aissue+is%3Aclosed), issues to make sure somebody else hasn't already reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+* A reproducible test case or series of steps
+* The version of code being used
+* Any modifications you've made relevant to the bug
+* Anything unusual about your environment or deployment
+
+## Contributing via Pull Requests
+
+Contributions via pull requests are much appreciated. Before sending a pull request, please ensure that:
+
+1. You are working against the latest source on the *Enhancements* branch.
+1. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+1. You open an issue to discuss any work - I'd hate for your time to be wasted.
+
+To send a pull request, please:
+
+1. Create an issue and discuss the change.
+1. Fork the repository.
+1. Checkout the *Enhancements* branch
+1. Modify the source; please focus on the specific change you are contributing. Please refrain from code styling changes, it will be harder to focus on your change.
+1. Ensure local tests pass.
+1. Commit to your fork using clear commit messages with the issue # being fixed.
+1. Send a pull request, answering any default questions in the pull request interface.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+## Finding contributions to work on
+
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/techthoughts2/Diag-V/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issues is a great place to start.
+
+## Code of Conduct
+
+This project has a [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Licensing
+
+See the [LICENSE](LICENSE.txt) file for our project's licensing.

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,38 @@
+---
+name: Bug Report
+about: Submit a bug to Diag-V project
+title: 'Diag-V bug issue'
+labels: bug
+assignees: ''
+
+---
+
+<!--- Provide a general summary of the issue in the Title above -->
+
+### Expected Behavior
+<!--- Tell us what should happen -->
+
+### Current Behavior
+<!--- Tell us what happens instead of the expected behavior -->
+
+### Possible Solution
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+
+### Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+### Context (Environment)
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Include as many relevant details about the environment where the bug was discovered. -->
+* Operating System and version as reported by `$PSVersionTable.OS`:
+* PowerShell versions as reported by `$PSVersionTable.PSEdition`:
+
+<!--- Provide a general summary of the issue in the Title above -->
+
+### Detailed Description
+<!--- Provide a detailed description of the issue you are facing -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for Diag-V project
+title: 'Diag-V Feature request'
+labels: 'enhancement'
+assignees: ''
+
+---
+
+### Description
+<!--- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+### Describe the solution you'd like
+<!--- A clear and concise description of what you want to happen. -->
+
+### Describe any alternatives you've considered
+<!--- A clear and concise description of any alternative solutions or features you've considered. -->
+
+### Additional context
+<!--- Add any other context or screenshots about the feature request here. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,21 @@
+# Pull Request
+
+**IMPORTANT: Please do not create a Pull Request without creating an issue first.**
+
+## Issue
+
+**(REQUIRED)** Issue #:
+
+### Closing Issues
+
+Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes.
+
+## Description
+
+Description of changes:
+
+<!-- Please provide enough information so that others can review your pull request -->
+
+## License
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

.gitignore

@@ -1,4 +1,12 @@
 Archive
 Artifacts
-.vscode
-cov.xml
+cov.xml
+# OS generated files #
+######################
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db

.vscode/extensions.json

@@ -0,0 +1,9 @@
+{
+    // See http://go.microsoft.com/fwlink/?LinkId=827846
+    // for the documentation about the extensions.json format
+    "recommendations": [
+        "ms-vscode.PowerShell",
+        "ryanluker.vscode-coverage-gutters",
+        "DavidAnson.vscode-markdownlint"
+    ]
+}

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+    "files.trimTrailingWhitespace": true,
+    "powershell.codeFormatting.preset":"Stroustrup"
+}

.vscode/tasks.json

@@ -0,0 +1,60 @@
+// Available variables which can be used inside of strings.
+// ${workspaceRoot}: the root folder of the team
+// ${file}: the current opened file
+// ${relativeFile}: the current opened file relative to workspaceRoot
+// ${fileBasename}: the current opened file's basename
+// ${fileDirname}: the current opened file's dirname
+// ${fileExtname}: the current opened file's extension
+// ${cwd}: the current working directory of the spawned process
+{
+    // See https://go.microsoft.com/fwlink/?LinkId=733558
+    // for the documentation about the tasks.json format
+    "version": "2.0.0",
+    // Start PowerShell
+    "windows": {
+        //"command": "${env:windir}/System32/WindowsPowerShell/v1.0/powershell.exe",
+        "command": "${env:ProgramFiles}/PowerShell/6/pwsh.exe",
+        //"command": "${env:ProgramFiles}/PowerShell/7-preview/pwsh.exe",
+        "args": [
+            "-NoProfile",
+            "-ExecutionPolicy",
+            "Bypass"
+        ]
+    },
+    "linux": {
+        "command": "/usr/bin/powershell",
+        "args": [
+            "-NoProfile"
+        ]
+    },
+    "osx": {
+        "command": "/usr/local/bin/powershell",
+        "args": [
+            "-NoProfile"
+        ]
+    },
+    // Associate with test task runner
+    "tasks": [
+        {
+            "label": "Test",
+            "group": {
+                "kind": "test",
+                "isDefault": true
+            },
+            "command": [
+                "Write-Host 'Invoking Pester...'; $ProgressPreference = 'SilentlyContinue'; Invoke-Pester -Script test -PesterOption @{IncludeVSCodeMarker=$true};",
+                "Invoke-Command { Write-Host 'Completed Test task in task runner.' }"
+            ],
+            "problemMatcher": "$pester"
+        },
+        {
+            "label": "Build",
+            "type": "shell",
+            "group": {
+                "kind": "build",
+                "isDefault": true
+            },
+            "command": "$psversiontable;Invoke-Build"
+        }
+    ]
+}