# What is being generated by NubesGen?
NubesGen generates a set of Terraform or Biceps configurations. If you selected the GitOps option, it will also generate a GitHub Action.
# Sample projects
Sometimes the best way to learn is to read directly the source code!
We maintain a complete set of sample projects that are used in our tests - so if the tests are green, you are guaranteed to have this output.
- Azure Container Apps + Docker + GitOps (opens new window)
- Azure Container Apps + Spring Boot + Maven + GitOps (opens new window)
- Azure Container Apps + Spring Boot + Maven + PostgreSQL + Key Vault (opens new window)
- App Service + Java + Maven + GitOps (opens new window)
- App Service + Java + Gradle + GitOps (opens new window)
- App Service + Java + Spring Boot + PostgreSQL + Azure Key Vault (opens new window)
- App Service + Java + Spring Boot + MySQL (opens new window)
- App Service + Java + Quarkus + MySQL (opens new window)
- App Service + Java + Spring Boot + PostgreSQL (opens new window)
- App Service + Java + Spring Boot + Redis (opens new window)
- App Service + Java + Spring Boot + Azure SQL (opens new window)
- App Service + Java + Spring Boot + Blob Storage (opens new window)
- App Service + Java + Application Insights (opens new window)
- App Service + Docker + GitOps (opens new window)
- App Service + .NET + GitOps (opens new window)
- App Service + Node.js + GitOps (opens new window)
- App Service + Java + Quarkus (opens new window)
- App Service + Java + Spring Boot (opens new window)
- App Service + Docker + VNet (opens new window)
- App Service + Java + App Insights + Key Vault + PostgreSQL + VNet (opens new window)
- Azure Spring Apps + Java + Application Insights + CosmosDB + Key Vault + Redis + Blob Storage (opens new window)
- Azure Spring Apps + Java + Application Insights (opens new window)
- Azure Spring Apps + Java + MySQL + GitOps (opens new window)
- Azure Spring Apps + Java (opens new window)
- Azure Spring Apps + Java + Key Vault + Azure SQL (opens new window)
- Azure Spring Apps + Java + Application Insights + CosmosDB + Key Vault + Redis + Blob Storage + VNet (opens new window)
- Azure Spring Apps + Java + VNet (opens new window)
- Azure Spring Apps + Java + Azure SQL + VNet (opens new window)
- Azure Spring Apps + Java + MySQL + VNet (opens new window)
- App Service + Java + Spring Boot + CosmosDB (opens new window)
- Azure Functions + Java + Spring Boot + Maven + GitOps (opens new window)
- Azure Functions + Java + Spring Boot + MySQL (opens new window)
- Azure Functions + Java + Application Insights + CosmosDB + Key Vault + PostgreSQL + Redis + Blob Storage + VNet (opens new window)
# Infrastructure as Code configuration files
NubesGen generates a .tgz
or a .zip
file.
Unzipping that file provides a similar structure:
- terraform
|- modules
|- app-service
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf
|- mysql
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf
In this example, we have a Terraform configuration that uses two modules (App Service and MySQL), that are ready for deployment.
To deploy your infrastructure, all you need to do is initialize Terraform and apply its configuration:
terraform init && terraform apply -auto-approve
# GitHub Action
If you selected the GitOps option, NubesGen will generate a GitHub Action for you, which will manage the Terraform configuration automatically.
That GitHub Action is located in a hidden GitHub directory, so the file structure will look similar to this:
– .github
|- workflows
|- gitops.yml
- terraform
|- modules
|- app-service
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf
|- mysql
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf
|- main.tf
|- outputs.tf
|- README.md
|- variables.tf