Are you a cloud native developer?

Was bedeutet es, ein "cloud nativer" Entwickler zu sein, wie sieht ein entsprechender Workflow dazu aus, welche Tools kommen zum Einsatz? Wie spielen Konzepte und Tools von GitHub, Hashicorp und Microsoft zusammen?
Die Fragen dazu möchten wir mit euch mittels einer Hands-On Session beantworten.

Lasst uns gemeinsam mit Hilfe von 'Visual Studio Code' und 'GitHub Codespaces' Cloud Ressourcen mittels 'Infrastructure as Code' definieren und deployen. Zudem werden wir auch zusammen Befehle für das Command Line Interface zu Kubernetes Clustern ausführen.

Der volle Inhalt:
* Erstellung deines eigenens GitHub Codespaces
* Installieren der Extension für GitHub Codespaces für Visual Studio Code
* Definieren einer Azure ressource mittels einer Terraform Configuration
* Provisionieren der Ressource in einer Azure Subscription mittels Terraform
* Deployment von Kubernetes Jobs auf einem Kubernetes Cluster
* Skalieren der Workloads
* Zerstören der Ressourcen in der Azure Subscription

Was du dafür brauchst:
* einen Laptop (ideal deinen privaten Laptop)
* einen GitHub Account
* Visual Studio Code

AI combined with cloud computing and infrastructure as a code - does that fit? Yes, indeed!

Are you curious how the GitHub Copilot could support you in implementing 'Infrastructure as Code' to deploy resources on Azure in an automated way?
This talk reveals my approach to using the AI pair programming tool. Starting from scratch, I will create a working Terraform configuration that can deploy a Kubernetes cluster on Azure, by just providing comments.
What could good practice for that look like?
It shall prove that AI speeds up your development speed and works well for infrastructure as code approaches.

According to the very last question of my lecture:
My response to this question was not very precise, and I would like to improve it by directly referring to GitHub Copilot, as the GitHub Copilot took up a significant part of my presentation. A search on the ‘GitHub Copilot Trust Center’ addressed the question of whether any prompts provided to the tool is stored:

"Does GitHub Copilot retain any of your prompts that it used as a basis for providing suggestions?"

Answer:
"The GitHub Copilot extension in the code editor does not retain your prompts for any purpose after it has provided Suggestions, unless you are a Copilot Individual subscriber and have allowed GitHub to retain your prompts and suggestions."

Source: https://resources.github.com/copilot-trust-center/