CPEX launch criteria attestation automation requirements

[ladonnaq]

This epic will identify the requirements needed to enable the automation of the attestation of the APEX launch criteria. We will identify requirements for Phase 1 and 2. If time permits, we may implement phase 1 toward end of Gallium. Given the loss of engineering resources, we have to prioritize the release planner functionality so we can onboard teams. Phase 2 cannot be achieved without the release planner.

Scenario Today

1. Service partners have to provide evidence for completion of APEX launch criteria via email, forms, teams channels, etc.
2. This evidence is then evaluated by the Azure SDK PM team to ensure that the criteria is met. The Azure SDK PM team copies the evidence into the appropriate field in the Azure Devops work item. The Azure SDK PM confirms that they service partner can mark the APEX launch criteria complete, N/A, or request an extension.
3. Next the Service Partner has to manually update Cloud Lifecycle to mark the launch criteria as complete, N/A, or request an extension.
4. Azure SDK PM team has to manually go approve the attestation of the launch criteria in S360 approval hub.

Between now and June 2023 there are currently 157 product launches that required APEX launch criteria validation.
This is a manual process that is time consuming for both the service partner and the Azure SDK PM team. Being manual, it is also more prone to errors.

Automating the APEX launch criteria state

• ADO Fields added that correspond to the launch criteria: Add data fields in ADO Epic product type for each of the Azure SDK APEX requirements (launch criteria)
• SDK Release Readiness APEX milestone: Remove manual steps and process  #7575
• Update Onboarding feature to automate the identifying APEX release scenarios  #7084
• Onboarding apex scenarios follow up work #8947
• Improvements to the "create a release plan" related to APEX process #9816
• [Backend- Release Plans] Pre-requisites data automation for attestation automation of APEX launch criteria (S360 KPIs)  #8225
• New initial Beta and new initial Stable SDKs need to be identified in the create a release plan flow  #7492

Phase 3 Design and Requirements to automate attestation

• @maririos The information gathered is based on what the docs team did. The docs team does not have a Release Planner app (Power Apps). So all of the data values are in the ADO fields. We have a Release Planner App with dataverse. The launch criteria evidence for sign-off is in the release plan. It might be easier to automate by pushing the data values to the S360 Cloud Lifecycle Kustos cluster from dataverse vs the ADO.
• @maririos Review the information provided on the CLC wiki page for providing evidence stream/automation - https://eng.ms/docs/cloud-ai-platform/azure-edge-platform-aep/aep-engineering-systems/engineering-intelligence-standards/service-360/service-360-team-docs/cloudlifecycle/createlcs#provide-evidence-stream-automate-approvals
• @maririos Review the Docs team overview of how they implemented automation of the attestations of their launch criteria - https://microsoft-my.sharepoint.com/:b:/p/svineet/ETSYZbrCIPdGrq9fiy4_kmwB2_28HzgyXasgrvAhdV45JA?e=ZdEqnb and https://github.com/orgs/Azure/projects/359/views/13?filterQuery=-status%3ADone&pane=issue&itemId=15857866
• @maririos Meeting recording for initial discussions around SDK PLR KPI Automation with APEX/CLC engineering - https://microsoft-my.sharepoint.com/:v:/r/personal/srmantha_microsoft_com/Documents/Recordings/SDK%20PLR%20KPI%20Automation-20231213_121247-Meeting%20Recording.mp4?csf=1&web=1&nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=2csk56
• Write design and requirements doc for implementation.
• Implementation

[ladonnaq]

@live1206 @josefree We should start on this work in parallel with the new UI. We have a dependency from the Azure Global APEX team to automate the attestation of the APEX launch criteria for Gallium. This is part of the overall push for automation and "default-green" for all S360 KPI action items. Let's talk through this github issue when we meet next week.