Azure Testing Framework/Library project
Перейти к файлу
jessica-ern 59a2644e76
expose gRPC endpoint for deploying at the subscription scope (#24)
* expose gRPC endpoint for deploying at the subscription scope

* not the template name I wanted
2022-11-10 13:38:33 -06:00
.devcontainer added gRPC requirements for python (#19) 2022-11-08 10:47:11 -06:00
.github/workflows Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
BenchPress Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
config/megalinter Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
docs added gRPC requirements for python (#19) 2022-11-08 10:47:11 -06:00
engine expose gRPC endpoint for deploying at the subscription scope (#24) 2022-11-10 13:38:33 -06:00
framework Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
protos expose gRPC endpoint for deploying at the subscription scope (#24) 2022-11-10 13:38:33 -06:00
samples Update to PowerShell Sample Code after Running in the Dev Container (#34) 2022-10-31 15:32:41 -04:00
.editorconfig configure code analysis in csharp projects (#24) 2022-10-24 09:57:59 -07:00
.gitignore Feature/megalinter (#18) 2022-10-20 17:38:35 -04:00
.gitmodules Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
.globalconfig Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
.mega-linter.yml GitHub Actions Pull Request Workflow - On Pull Request to Specific File Path, only the required file path will be linted instead of running all linting workflow (#11) 2022-11-04 10:45:23 -04:00
.pylintrc Feature/python sample tests (#27) 2022-10-28 10:32:54 -07:00
BenchPress.sln Bicep Transpile Service - Takes Bicep File, Generates Arm Template Using Bicep Submodule (#20) 2022-11-09 15:03:54 -05:00
CODE_OF_CONDUCT.md creating code of conduct 2022-08-15 19:32:33 -07:00
CONTRIBUTING.md Feature/megalinter (#23) 2022-10-24 15:22:02 -04:00
LICENSE LICENSE committed 2022-04-22 15:57:07 -07:00
README.md Feature/pws sample (#28) 2022-10-28 10:54:14 -04:00
SECURITY.md GitHub Actions Workflow for Linting python and dotnet source code, and docs (#22) 2022-10-24 14:15:59 -04:00
SUPPORT.md GitHub Actions Workflow for Linting python and dotnet source code, and docs (#22) 2022-10-24 14:15:59 -04:00
package-lock.json Feature/megalinter (#18) 2022-10-20 17:38:35 -04:00
package.json Feature/megalinter (#18) 2022-10-20 17:38:35 -04:00

README.md

Bicep testing framework

This framework is intended to work as a testing framework for Azure deployment features by using Bicep.

In order to see how you can work with this framework you can find one sample bicep file in the folder samples that will be deployed by using one PowerShell script.

Process is the following:

flowchart LR

A[Creation] -->|Bicep| B[Verification]
B --> C[Remove]

Creation: New Features are gonna be deployed through Bicep files Verification: Test is going to confirm the resource exists and also assert if it matches the expected value Remove: Optionally resources can be removed after being tested

Getting started

See Getting Started guide on how to start development on Benchpress.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.