Handcrafted, AI-free blog posts about DevOps, DevSecOps, application security, web development, Azure and similar topics
The author sought a method to identify inactive GitHub Copilot Business license users. After troubleshooting errors, they successfully implemented a reminder workflow and contributed improvements.
This week, I faced challenges deploying an ASP.NET Core Web API to an Azure App Service using GitHub Actions and OpenID Connect. Initial attempts with azure/webapps-deploy@v3 failed due to missing credentials. A later try with azure/cli@v2 failed because the deployment file wasn't a valid zip. Properly zipping the files led to successful deployment.
The blog post details the process of rotating secrets stored in Azure Key Vault with each application deployment, utilizing Infrastructure as Code (IaC) principles via Terraform. It emphasizes the importance of secret rotation to minimize risks from leaks. An ASP.NET Core Web API is demonstrated as the application example, alongside procedural GitHub Actions for deployment.
GitHub announced the re-deployment of content exclusions, allowing repo administrators and organization owners to manage content exclusion settings for GitHub Copilot. It's in beta for Copilot Business subscribers and supported in various IDEs. Exclusions can be set for specific files, files in any Git-based repo, or a whole repo.
This blog post is a personal assessment of GitHub Copilot based on a 60-days free trial usage and information I gathered from different sources. Let's start with a short introduction. What IT IS GitHub Copilot got announced as Your AI pair programmer. It's an artificial intelligence (AI) based service that supports developers in writing code... Continue Reading →
blog.rufer.be 