Etablere YT-miljø

[arealmaas]

Acceptance criteria'ish:

• A new environment for application/infrastructure should be established (test, staging, yt01, prod)? ✅
• The new YT-environment should use YT-specific integrations ✅
• The environment should match the resources in production to ensure a good test. Ensure we have an upgraded SKU here for prod/YT

Establish infrastructure for YT

• Add new Bicep bicepparam, new workflow entry ✅
• Should mirror production environment in terms of resource SKUs etc ✅
• Upgrade the SKU in both YT and prod

Establish new applications for YT

• Add new Bicep bicepparam, new workflow entry ✅

• New appsettings

  • Altinn: https://platform.yt01.altinn.cloud ✅
  • Maskinporten: ✅
  • Events: ✅
  • IDporten: ✅
  • New subscription-key ✅

Establish APIM

• Set up APIM to point to new container apps ✅

Deployments:

• Set up new environment in Github ✅
• Deploy when we deploy to staging?) ✅
• Should we run e2e-tests? ✅

Other actions:

• Verify access to all endpoints ✅
  • Check if we have access to the event-endpoint
  • Does Maskinporten and IDPorten have YT-environment? Or what do they expect
• What is the name of this baby(environment)? ✅ yt01
• To ensure we can replicate web-api horizontally, we need to spin up a new container to consume the events (new task) ✅

[elsand]

I've added ten test resources to the resource registry in YT01 named ttd-dialogporten-performance-test-01 through ttd-dialogporten-performance-test-10. They all have the same policy granting read, write, publish, subscribe (the latter two for events) to PRIV and DAGL.

[arealmaas]

Await SKU upgrade before we do the first test 👍