Azure
/
benchpress
зеркало из https://github.com/Azure/benchpress.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
benchpress/CONTRIBUTING.md

15 KiB
Исходник Ответственный История

Contributing to BenchPress

Thank you for your interest in the BenchPress open-source project for testing Infrastructure as Code in Azure.

There are several ways to contribute to BenchPress including: identifying and reporting issues, contributing to the code and documentation.

Please review the Code of Conduct and the Contributor License Agreement.

Local Environment Setup

There are two methods to getting a development environment up and running: local setup and using a dev container.

Local Setup

Using a local setup either VS Code or Visual Studio can be used to develop code for the BenchPress project. VS Code is the recommended IDE, but Visual Studio will work as well. For this guide we will cover VS Code prerequisites:

  1. Install PowerShell Modules:
    • Azure PowerShell Module: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser Install-Module -Name Az -Scope CurrentUser -Repository PSGallery -Force Install-Module -Name Az.App -Scope CurrentUser -Repository PSGallery -Force Install-Module -Name Az.Portal -Scope CurrentUser -Repository PSGallery -Force Install-Module -Name Az.Search -Scope CurrentUser -Repository PSGallery -Force
    • Pester: Install-Module -Name Pester -Force -SkipPublisherCheck.
  2. Install Visual Studio Code.
  3. Install node.js (required for running megalinter).
  4. Install VS Code Extensions:
    • Azure CLI Tools
    • Bicep
    • C#
    • Docker
    • EditorConfig
    • PowerShell
    • Prettier (used for local linting)

Dev Container

The BenchPress repository contains a definition for a dev container. In order to use the dev container:

  1. Install VS Code Extensions:
    • Dev Container
    • WSL
  2. Ensure that Docker Desktop or other container hosting engine is installed and running.
  3. Open the BenchPress repository folder in VS Code.
  4. From the command window (Ctrl + Shift + P) choose "Reopen in Container".

The BenchPress dev container is configured to provide the developer with all of the tools necessary to write and test code for BenchPress.

Using WSL2 with a Dev Container

If your Docker Desktop or other container host is using WSL2, then there might be severe lag when using VSCode with a dev container when the code is hosted on the Windows subsystem. In order to remediate this it is recommended to use the WSL2 subsystem with the dev container.

  1. Install the Remote Development Extension Pack Extension in VSCode.
  2. If WSL2 is not installed, install WSL2. From a Windows Terminal execute wsl --install and then open a WSL terminal.
  3. From a terminal in WSL2:
    1. Install the .NET SDK: sudo apt-get update && sudo apt-get install -y dotnet-sdk-7.0
    2. Install .NET Core: sudo apt-get update && sudo apt-get install -y dotnet-runtime-7.0
    3. Restart the WSL terminal.
    4. Create a directory for source code and cd into it.
    5. Clone or fork the repo as described in Contributing to Code and Documentation
    6. cd into the repo's directory
    7. Open VSCode from the command line with: "code ." (or "code-insiders ." if using the VS Code Insiders build)
    8. From the command window (Ctrl + Shift + P or Command + Shift + P) choose Reopen in Container

Running Megalinter in a Dev Container

Because megalinter executes in a container within the dev container the mapped paths are mapped to the container path, but executed against the host path. This requires that the docker command that would normally be executed with mega-linter-runner be adjusted for the host path:

  • Specific folder (recursively): docker run --rm -v /var/run/docker.sock:/var/run/docker.sock:rw -v <host path to folder>:/tmp/lint:rw oxsecurity/megalinter-dotnet:v6

  • Specific file (or comma separated files): docker run --rm -v /var/run/docker.sock:/var/run/docker.sock:rw -v <host path to folder>:/tmp/lint:rw -e SKIP_CLI_LINT_MODES=project -e MEGALINTER_FILES_TO_LINT=<relative path to file(s) from folder> oxsecurity/megalinter-dotnet:v6

Module Development

BenchPress is designed to be extensible. You can create your own modules and contribute them to the community.

A valid module must have these files;

Modules/BenchPress.Azure/Public
└───Confirm-{Resource Type Name}.ps1

Modules/BenchPress.Azure/Tests/Public
└───Confirm-{Resource Type Name}.Tests.ps1

examples/{Resource Type Name}
├───{Resource Type Name}.Tests.ps1
├───{Resource Type Name}.bicep
└───{Resource Type Name}_Example.md

"{Resource Type Name}" {
  return Confirm-{Resource Type Name} -ResourceGroupName $ResourceGroupName -Name $ResourceName
}

Module Testing

  • Run the following command in the root directory of the project to create a local copy of BenchPress in the bin folder;
.\build.ps1 -Import

Other commands available in the build.ps1 can be found in the Installation.md#Install the BenchPress Module from the Local File System section

Invoke-Pester -Script examples/{Resource Type Name}/{Resource Type Name}.Tests.ps1

What if the resource type is not in the Azure PowerShell module?

If the resource type is not in the Core Azure PowerShell module (Az), you have to do the following steps;

  • Find the module that contains the resource type. For example, Az.Portal module contains the Azure Dashboard resource type.

  • Add the module installer to ci.yml file.

Install-Module -Name Az.{ModuleName} -Scope CurrentUser -Repository PSGallery -Force

Install-Module Az.{ModuleName} -ErrorAction Stop
  • Add the module importer to the beginning of the Modules/BenchPress.Azure/Public/Confirm-{Resource Type Name}.ps1 file;
Import-Module Az.{ModuleName}
  • Add the module importer to the beginning of the Modules/BenchPress.Azure/Tests/Public/Confirm-{Resource Type Name}.Tests.ps1 file;
Import-Module Az.{ModuleName}

Reporting Issues

  1. Check the Issue Tracker to determine whether the issue that you're going to file already exists.
    1. If your issue exists (all inputs and relevant information is identical to an existing issue):
      1. Make relevant comments to add context that helps broaden understanding or helps identify the root concern.
      2. Add a reaction to upvote (👍) or downvote (👎) an issue.
    2. If the issue does not exist create a new issue with the following guidelines:
      • Do not submit multiple problems or features in a single submitted issue.
      • Provide as much information as possible. The more information provided, the more likely that someone will be successful in reproducing the issue and identifying the cause. Provide as much of the following information as possible (not an exhaustive list):
        • Version of PowerShell being used.
        • The operating system and version being used.
        • Any container information, if used.
        • An ordered list of reproducible steps that cause the issue to manifest.
        • Expecations versus reality. What was expected to happen versus what actually happened.
        • Any images, gifs, animations, links, videos, etc. that demonstrate the issue.
        • A code snippet or link to a repository that contains code that reproduces the issue.

Contributing to Code and Documentation

In order to setup a local environment to contribute to BenchPress review the Local Environment Setup.

Once an issue has been created or identified to contribute to, the following steps can be followed to contribute to the BenchPress code and documentation:

  1. Clone or fork the repository. Clone if you have permissions, fork if you do not.
  2. Ensure the latest code is available locally by executing git fetch all.
  3. Create and checkout a feature branch using the number of the issue in a feature\<issue #> branch. For example: git checkout -b feature\123.
  4. Make the changes necessary to address the issue.
  5. Commit the final changes to the feature branch using git commit
  6. Push change to the fork or clone.
  7. Create a Pull Request from the pushed branch if the repository was cloned or from the fork/branch if the repository was forked.
  8. If necessary address any automated Pull Request checks by making fixes on the local feature branch and pushing the fixes when completed. Repeat this process until all PR checks have been resolved.

Contribution Standards

  1. Code - It is intended that all code contributions conform to the guidelines found at the following references (listed in the order of precedence when there is a conflict):
    1. Microsoft Strongly Encouraged Development Guidelines
    2. PowerShell Practice and Style Guide
    3. Additional guidance:
      1. Multi-line code with piped commands - when the pipe is the first character of the line, the pipe will align to the left edge of the start of the previous line's command (i.e., not indented past the start of the previous line's command and not flush to the left at column 0).
  2. Docs - It is intended that all documentation contributions conform to the guidelines found at the following references (listed in the order of precedence when there is a conflict):
    1. Microsoft PowerShell-Docs Style Guide

Requirements for submitting functions or classes

  • It is required that there is one file per class/function.
  • Functions will be written to .ps1 files.
  • Classes will be written to .psm1 files.
  • The filename of a function must match the function name (e.g., Get-Something function must be in a file named Get-Something.ps1).
  • Any function that is used internally and not desired to be exposed via Export-ModuleMember must reside in the Private folder.
  • Any statements at the beginning of a file that import data from another relative file (e.g., using module, or dot sourcing another file), or that execute Import-Module must be at the top of the file, and must be preceded by a line with the content # INLINE_SKIP and followed by a line with the content # end INLINE_SKIP. These denote to the build script that content which will not be built into the final inline module script.
  • If you add a new Confirm-* cmdlet and resource type to Modules\BenchPress.Azure\Public, you must also:
    1. Add the cmdlet to the list of FunctionsToExport in Modules\BenchPress.Azure\BenchPress.Azure.psd1.
    2. Add a unit test in the Modules\BenchPress.Azure\Tests\Public folder.
    3. Add the new type to the generator code at BenchPress\Generators\ResourceTypes.
    4. Update Get-ResourceByType to add the ResourceType to the switch. If there are any new parameters for the cmdlet, those need to documented in the comments and added to the parameters that are accepted.
    5. If new parameters are added to Get-ResourceByType, those same parameters must also be added to Confirm-Resource to be passed through in the parameters hashtable and the comments updated appropriately.
    6. A new example must be created in the examples folder.
      • If the example is in the family of an existing resource, add the resource to the existing family's files. Otherwise, create a new folder for the new resource family.
      • For each new resource the following must be added (or updated):
        • A .md file that describes how to use the example.
        • A .bicep file that properly deploys the resource(s) to Azure.
        • A .Tests.ps1 file that tests the deployed resource(s) in Azure.
    7. The code author that creates an example from the previous step must deploy the resources to Azure and confirm that the tests properly execute before submitting a pull request.
    8. An example of merged code that meets the above criteria: PR

Thank You

Thank you for your interest and contribution to the BenchPress open-source project.

Code of Conduct

Please review and adhere to the tenents of the Code of Conduct before contributing.

Contributor License Agreement

To speed up the acceptance of any contribution to the BenchPress repository, you should sign the Microsoft Contributor License Agreement (CLA) ahead of time. If you've already contributed to BenchPress or Microsoft repositories in the past, congratulations! You've already completed this step. This a one-time requirement for the BenchPress project. Signing the CLA process is simple and can be done in less than a minute. You don't have to do this up-front. You can simply clone, fork, and submit your pull request as usual. When your pull request is created, it is checked by the CLA bot. If you have signed the CLA, the status check will be set to passing. Otherwise, it will stay at pending. Once you sign a CLA, all your existing and future pull requests will have the status check automatically set at passing.