Open massimobonanni opened 4 days ago
Thanks @massimobonanni. I'll review it since we are no longer using Service Principals. I may have missed something.
I have experienced the same issue in "Task 1: Setup and Run CI pipeline"
The error was: There was a resource authorization issue: "The pipeline is not valid. Job Build: Step AzureResourceManagerTemplateDeployment input ConnectedServiceName references service connection azure subs which could not be found. The service connection does not exist, has been disabled or has not been authorized for use. For authorization details, refer to https://aka.ms/yamlauthz. Job Build: Step DockerCompose1 input azureSubscriptionEndpoint references service connection azure subs which could not be found. The service connection does not exist, has been disabled or has not been authorized for use. For authorization details, refer to https://aka.ms/yamlauthz."
... indicating that the pipeline is trying to use a service connection named "azure subs", but that connection doesn't exist, maybe steps will be added to the guide to create this in future?
@massimobonanni @LewisGoDeploy that instruction will be updated to use the user email/name instead of Service Principal. I replaced Service Principals by Workload Identity federation in the Validate lab environment, "Create a service connection to access Azure resources".
Contact Details
massimo.bonanni@tiscali.it
What should we change?
I found a reference to a Service Principal creation in the lab M03-L05 ("Implement GitHub Actions for CI/CD"). I suggest to add same instructions to create the principal also in this lab. If the student make this lab without making the previous one, he/she cannot find the service principal and he/she has no idea how to create
Lab
Lab 10 Integrate Azure Key Vault with Azure DevOps
Relevant screenshots
paste here 😉