feat: deploy test apim in developer sku for testing purposes

[tjololo]

Description

To test alternatives to subscription keys there is a need to have a test apim to test alternatives

Related Issue(s)

• #{issue number}

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Summary by CodeRabbit

• New Features
  • Automated Infrastructure Deployment: Introduced a new workflow for planning and applying infrastructure changes. The process supports manual triggers with customizable log levels and ensures that changes are validated before deployment.
  • Enhanced Cloud Service Management: Upgraded API management capabilities and introduced dynamic resource grouping to improve scalability, reliability, and overall performance.

[coderabbitai]

Warning

Rate limit exceeded

@tjololo has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between b93dc64 and a66f76e.

📒 Files selected for processing (2)

• .github/workflows/altinn-apim-test-rg-deploy.yml (1 hunks)
• infrastructure/adminservices-test/altinn-apim-test-rg/terraform.tfvars (1 hunks)

📝 Walkthrough

Walkthrough

This pull request introduces a new GitHub Actions workflow designed to automate Terraform planning and deployment. It defines two jobs—one for planning and one for deployment—with manual trigger options and conditional execution based on branch and job success. Additionally, several Terraform configuration files are added to deploy an Azure API Management service along with its associated resource group. Variable definitions and provider configurations for Azure are also included to enable dynamic deployment.

Changes

File(s)	Change Summary
.github/workflows/altinn-apim-test-rg-deploy.yml	New GitHub Actions workflow for Terraform: triggered on pushes, PRs, and manual dispatch; defines environment variables and two jobs (plan and deploy) to run Terraform plan and apply operations.
infrastructure/adminservices-test/altinn-apim-test-rg/{apim.tf, main.tf, rg.tf, variables.tf}	New Terraform configurations for Azure infrastructure: - apim.tf: Adds an Azure API Management resource. - main.tf: Sets up Terraform provider/ backend configurations for Azure. - rg.tf: Defines an Azure Resource Group resource. - variables.tf: Introduces deployment variables.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHubActions as GitHub Actions
    participant PlanJob as Plan Job
    participant DeployJob as Deploy Job

    Developer->>GitHubActions: Push/Pull Request or Manual Trigger
    GitHubActions->>PlanJob: Start Terraform plan
    PlanJob-->>GitHubActions: Return plan results
    GitHubActions->>DeployJob: Trigger deploy (if plan successful)
    DeployJob-->>GitHubActions: Execute Terraform apply

Loading

Suggested reviewers

• monteiro-renato

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Terraform environment test

Format and Style 🖌success

Initialization ⚙️success

Validation 🤖success

Validation Output

Success! The configuration is valid.

Plan 📖success

Show Plan

[Lines containing Refreshing state removed]
Acquiring state lock. This may take a few moments...

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # azurerm_api_management.admin_test_apim will be created
  + resource "azurerm_api_management" "admin_test_apim" {
      + client_certificate_enabled    = false
      + developer_portal_url          = (known after apply)
      + gateway_disabled              = false
      + gateway_regional_url          = (known after apply)
      + gateway_url                   = (known after apply)
      + id                            = (known after apply)
      + location                      = "norwayeast"
      + management_api_url            = (known after apply)
      + name                          = "altinn-apim-test-apim"
      + notification_sender_email     = (known after apply)
      + portal_url                    = (known after apply)
      + private_ip_addresses          = (known after apply)
      + public_ip_addresses           = (known after apply)
      + public_network_access_enabled = true
      + publisher_email               = "[email protected]"
      + publisher_name                = "Team-Platform"
      + resource_group_name           = "altinn-apim-test-rg"
      + scm_url                       = (known after apply)
      + sku_name                      = "Developer_1"
      + virtual_network_type          = "None"

      + delegation (known after apply)

      + hostname_configuration (known after apply)

      + protocols (known after apply)

      + security (known after apply)

      + sign_in (known after apply)

      + sign_up (known after apply)

      + tenant_access (known after apply)
    }

  # azurerm_resource_group.rg will be created
  + resource "azurerm_resource_group" "rg" {
      + id       = (known after apply)
      + location = "norwayeast"
      + name     = "altinn-apim-test-rg"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Saved the plan to: tfplan.out

To perform exactly these actions, run the following command to apply:
    terraform apply "tfplan.out"
Releasing state lock. This may take a few moments...

Context	Values
Pusher	@tjololo
Action	push
Working Directory	./infrastructure/adminservices-test/altinn-apim-test-rg
State File	github.com/altinn/altinn-platform/environments/test/altinn-apim-test-rg.tfstate
Plan File	github.com_altinn_altinn-platform_environments_test_altinn-apim-test-rg.tfstate.tfplan

[bengtfredh]

LGTM