Граф коммитов

15 Коммитов

Автор SHA1 Сообщение Дата
Ben Broderick Phillips cc0718c4d7
Migrate image and dotnet tool publish to 1es pipelines (#7920)
* Migrate to 1es pipelines

* Update build-tools tag
2024-03-20 15:17:51 -04:00
Ben Broderick Phillips 50444bee3a
Add otel collector to image publish pipeline (#7772) 2024-02-27 14:57:02 -05:00
Liudmila Molkova fc8986203a
Add dockerfile for HTTP fault injector (#7199)
* add dockerfile for fault injector
2023-11-09 17:41:10 -08:00
Konrad Jamrozik 80de661dc5
Update Ubuntu `18.04` to `2X.04` ; update `MMSUbuntu2X.04` to `ubuntu-2X.04` (#6004)
* Migrate Ubuntu 18.04 to 20.04 or 22.04, as appropriate

* MMSUbuntu22.04 -> ubuntu22.04

* MMSUbuntu20.04 --> ubuntu-20.04

* revert sdk-testgen ci.yml to MMSUbuntu22
2023-04-19 22:26:17 -07:00
Konrad Jamrozik 2bcb4d62cd
Update Ubuntu images to 1ES-hosted Ubuntu 22.04 in many places (#4996)
https://github.com/Azure/azure-sdk-tools/pull/4996
2023-01-03 17:43:09 -08:00
Scott Beddall df4815df33
Add Support for `Docker Manifest` publishing to `publish-docker-image.yml` (#3115)
* documenting the process to create a manifest, updating the linux dockerfile to allow multiplatform build
* deleting previous testproxy-lin-arm64 image in favor of re-used linux dockerfile with build argument
* using new pools. updating existing infra to use new pools. 
* update prepare.ps1 to also install qemu if necessary
* publishing multiplatform manifest!

Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
2022-04-11 14:11:33 -07:00
Scott Beddall 8c67cde139
correct docker image tagging to have missing period (#2814) 2022-02-24 16:15:29 -08:00
Scott Beddall 4ff0bc6279
Making `docker` automation available to users of `archetype-sdk-tool-dotnet` (#2803)
* Add InformationalVersion to test-proxy csproj. This will display the nuget version that this version of the test-proxy dll was built for
* update test-proxy code in Startup.cs to output the full build number 
* Move containers/ci.yml docker logic to a common template that can be used elsewhere in the repo.
* Add docker container test/publish to archetype-tool-dotnet
2022-02-24 15:03:32 -08:00
ckairen f6a5c43a3e
updating container ci trigger (#2274) 2021-11-15 14:44:59 -08:00
ckairen c6f4a07e2f
Automate stress test eng-common-tools dockerfile release pipeline (#2198)
* automate stress test eng-common-tools dockerfile release pipeline

* changing script and dockerfile paths
2021-11-02 22:05:43 -07:00
Ben Broderick Phillips dd1c8ca2a8
Fully automate stress cluster buildout and add support for azure file share mounting (#2106)
- Fully automate cluster buildout. Add azure file share mount to stress tests.
    - Moving the test/ad-hoc cluster back to the playground subscription
    - Upgrading kubernetes cluster version to 1.21.x to pull in support for the azure csi file driver
    - Adding high memory agent nodes to the base deployment
    - Enabling node autoscaler in the base deployment
- Publish stress watcher image in CI. Run docker build on PR
    - Using common image location across stress clusters to simplify buildout+deployment
- Add stress test debug file share usage example

Resolves #1903
2021-10-22 22:08:10 +00:00
Scott Beddall c0d142ae04
[Test-Proxy] eng/common templates (#1909)
Changes in this PR:
- Add test proxy tool and docker invocations to the eng/common yaml.
- Update eng/common with the SSL-related items so they can be trusted by language-specific tooling
- Update documentation and build to reflect new certificate files location.

Ok. @weshaggard I have added a `prepare.ps1` to the `test-proxy/docker` folder. Updated the documentation that refers to the certificate by name/location. Updated the docker build to be able to run the `prepare.ps1` script. 

[Successful Test invocation using these location changes in sdk-for-python](https://dev.azure.com/azure-sdk/playground/_build/results?buildId=1050334&view=results)
[Successful Test container publish](https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1050428&view=logs&j=c370c9e0-ef2e-5a74-495e-4719e52f70ec&t=21eced4c-c8be-5dcb-8a86-9b163bc55754)
2021-08-17 00:18:39 +00:00
Maor Leger 320bfa8a1b
Move the mock attestation service to azure-sdk-tools (#1882)
## What

- Add `keyvault-mock-attestation` code to the azure-sdk-tools
- Dockerize the code to prepare for adding it to the azsdktools ACR registry.

## Why

This mock service is needed to run live tests for a specific keyvault scenario. While we currently use the 
long-running test fixture that I deployed, that is not a sustainable solution. 

We want to make sure the code for this mock service is in a repo that is owned by Azure SDK team, 
and we want to enable test runs to deploy and tear down everything that need to run live tests. Depending
on a long running test fixture that is in my private repo violates both of these conditions. By moving the 
code here and ensuring that we can push updates to ACR we will be able to deploy the container for every
test run.
2021-08-10 13:25:35 -07:00
Scott Beddall 653e51f2af
[Test-Proxy] Windows Image, Additional Documentation, Certificate Update. (#1879)
* Lots of documentation updates (around SSL and the like)
* Adding `windows` version of the container, so that our windows machines in devops can load
* Renaming from `ubuntu_testproxy` to `testproxy` because the manifest will figure out which one you need
* Updating the default `pfx` that we install on the docker images to have a password, such that you don't hit issues when you try to import it with `-p ""`. On pshell it can take that as "not passing" a required argument. Lets just avoid that.
2021-08-05 17:51:15 -07:00
Scott Beddall 6c86090f21
Merging test-proxy to `main` (#1785)
This commit adds a C# tool package called `test-proxy`. The proxy is intended to enable out-of-process recordings for any language.

Included
 * Test-proxy and accompanying test project 
   * Extended readme to assist with installation and running via docker or .NET.
   * Built with .NET 5.0, installable via `dotnet tool install`.
   * Supports both in-memory and persisted storage playback.
   * Supports adding sanitizers, matchers, and transforms to either an entire session or an individual recording. 
   * Allows extensive manipulation of any part of a recording via regex sanitization.
   * Available sanitizers, matchers, and transforms are documented by runtime access of the comment XML. Available at <proxy-host-url>/Info/Available.
   * Copies` x-ms-client-id` and `x-ms-client-request-id` from the request to the response during playback.
   * Proxy handles gzip compressed responses. Gzipped responses are written to disk uncompressed to enable proper storage, sanitization, and transformation. Re-zipped prior to sending to requester.
 * Multiple sample projects in .NET and Python to give examples of interaction with the proxy.
 * Docker Container (along with yml publishing of said container) that abstracts installation and running of the proxy.
 * Example startup scripts in python, powershell, and js. These abstract the docker invocation and are easily applicable to language-specific test frameworks.

Co-authored-by: Mike Harder <mharder@microsoft.com>
Co-authored-by: Krista Pratico <krpratic@microsoft.com>
2021-07-09 10:58:36 -07:00