Aurélien Bombo 9dd3807467 ci: Use OIDC to log into Azure ... This completely eliminates the Azure secret from the repo, following the below guidance: https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-azure The federated identity is scoped to the `ci` environment, meaning: * I had to specify this environment in some YAMLs. I don't believe there's any downside to this. * As previously, the CI works seamlessly both from PRs and in the manual workflow. I also deleted the tools/packaging/kata-deploy/action folder as it doesn't seem to be used anymore, and it contains a reference to the secret. Signed-off-by: Aurélien Bombo <abombo@microsoft.com>		2025-06-06 15:26:10 -05:00
..
gha-run.sh	ci: Use OIDC to log into Azure	2025-06-06 15:26:10 -05:00
kata-deploy.bats	kata-deploy: Create runtimeclasses by default	2025-03-31 11:29:44 +01:00
run-kata-deploy-tests.sh	shellcheck: kata-deploy: Fix warnings	2025-03-05 19:44:27 +01:00