Infrastructure

[Noggling]

Today, our infrastructure is situated within the "pep-infra" environment, and it's crafted using Bicep. Within this repository, there's some legacy code pertaining to resources that are no longer in active use.

Furthermore, we share the same subscription with all CC applications and the JC portal, specifically the "S364-Johan Castberg Project Portal." This prompts the question: should the project portal have its dedicated subscription, or is it preferable to transfer our resources to the fusion subscription?

On the topic of Bicep, it's worth noting that I've observed a growing trend among other teams who are opting for Terraform in favor for Bicep. It appears that Terraform has gained popularity, with a growing number of individuals adopting it for their infrastructure provisioning needs.

We should aim to relocate the code to "fusion-project-portal-infra" to harmonize with the repository naming convention. In the event of transitioning to Terraform, starting with a clean slate. It would be greatly beneficial to receive an introduction to Terraform, enabling us to actively contribute and eventually perform fundamental tasks within the infrastructure repository.

The repository has been created but is set to private for now, with no additional user added.