Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where applicable, update Windows pools used to azsdk-pool-mms-win-2022-general and rename vmImage to the windows-20xx format #34163

Merged
merged 4 commits into from
Feb 17, 2023

Conversation

konrad-jamrozik
Copy link
Contributor

@konrad-jamrozik konrad-jamrozik commented Feb 15, 2023

Where applicable, update Windows pools used to azsdk-pool-mms-win-2022-general and rename vmImage to the windows-20xx format.

This discussion explains why we chose given vmImage format:

Mike Harder: 1ES Hosted Pool image name changes
posted in Azure SDK / Engineering System 🛠️ at Wednesday, February 15, 2023 12:10 PM

For further context, please see:

@konrad-jamrozik konrad-jamrozik added the Central-EngSys This issue is owned by the Engineering System team. label Feb 15, 2023
@konrad-jamrozik konrad-jamrozik self-assigned this Feb 15, 2023
@ghost ghost added Communication Storage Storage Service (Queues, Blobs, Files) labels Feb 15, 2023
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

@konrad-jamrozik konrad-jamrozik changed the title Update MMS2022 images to MMS2022Compliant + one storage pool update to 2022 Where applicable, update Windows pools used to azsdk-pool-mms-win-2022-general and rename vmImage to the windows-20xx format Feb 17, 2023
Konrad Jamrozik added 2 commits February 16, 2023 19:08
@@ -56,7 +56,7 @@
{
"Agent": {
"Windows2022": {
"OSVmImage": "MMS2022",
"OSVmImage": "windows-2022",
Copy link
Contributor Author

@konrad-jamrozik konrad-jamrozik Feb 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@benbp @mikeharder do you think that perhaps this line also need an update?

        "AZURE_TEST_AGENT": "WINDOWS_2019_NETCORE31"

I think this PR might have forgot to update it:

I am thinking: if CI passes, merge now without touching this, worry later :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea how AZURE_TEST_AGENT is used, but yeah I'd update the OS and net versions to match reality.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC this was a workaround I and ACS came up with due to restrictions with registered phone numbers being used in live tests (1:1 limit), and being able to dynamically look up which phone number needed to be used from the keyvault secret.

FYI @danielortega-msft we may need to think about how to keep this variable updated, as if we rev the version here it won't be able to find the secret.

Copy link
Contributor Author

@konrad-jamrozik konrad-jamrozik Feb 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@benbp @mikeharder for now I am going to merge this PR. If anybody has an idea if/how to update this string, I am happy to make another PR doing that.

@konrad-jamrozik konrad-jamrozik merged commit 2a2a91d into main Feb 17, 2023
@konrad-jamrozik konrad-jamrozik deleted the users/kojamroz/update_pools_to_compliant branch February 17, 2023 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. Communication Storage Storage Service (Queues, Blobs, Files)
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants