[Test-Proxy] eng/common templates

[scbedd]

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
Successful Test container publish

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[weshaggard]

I'm super conflicted about where to put dotnet-devcert.pfx/crt.

Lets start with only one under eng/common and I'd suggest having a script that can be used to setup the certificate even if it is a separate command from the docker run. We can then wait for feedback about what people end up doing and make adjustments as necessary. My hope is that most folks doing this locally won't need to care about the certificate at all.

[benbp]

@scbedd one possible solution: you could publish another docker image from tools that just contains the dev cert and the desired path, and then use multiple FROM directives to overlay your "test proxy assets" filesystem into the image build. That way you wouldn't need any external directory context, and could manage updates to the dev cert easily. You could then remove all these lines and make the dockerfile a little simpler.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[scbedd]

@benbp I am going to head this direction. First thing I'm going to do is force the build of the current dockerfile images from the root of the repo, thereby allowing access to the common assets. After that, I'll add two docker images that abstract the build of those assets. I would do it now, but I need to get this merged quickly.

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[ghost]

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.