Recently, whilst trying to run the following command in a GitHub Actions workflow script to create a new Release in my GitHub Repository:
gh release create XXXX --generate-notesHowever, strangely I encountered the following workflow error:
HTTP 403: Resource not accessible by integrationIf you’ve faced the same error, then you’re in luck – because I’ll be sharing the solution that worked for me to resolve this issue.
Continue readingDeploying resources to the cloud through deployment pipelines requires the need to authenticate with the various cloud providers in a standardised and secure manner. GitHub Actions offers the ability to authenticate with Azure using OpenID Connect (OIDC).
In this post, I’ll guide you through the process of setting up OpenID Connect (OIDC) authentication with Azure and GitHub Actions.
GitHub has really opened the doors for collaboration across the wider software development community. If you are already using GitHub then it makes sense to make the most of the GitHub ecosystem and use of all of it’s available features, including GitHub Actions; a powerful workflow engine that enables developers to automate repetitive tasks.
In this post I’ll show you how you can deploy an Azure Function using a GitHub Actions workflows, and by the end of this guide, you’ll have a fully working automated deployment pipeline setup.
Please note that this guide assumes that you are already familiar with using Azure Functions and using GitHub for basic source control management.
© 2024 Shane Bartholomeusz
Theme by Anders Noren — Up ↑