chore: add studioctl local configuration#1797
Conversation
|
Warning Review limit reached
More reviews will be available in 36 minutes and 33 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
studioctl app env --json --project <app>.STUDIOCTL_APP_RUN.Why
This lets IDE/debugger launches get the same local platform configuration as
studioctl run, while still keepingstudioctl runas the source of truth for local harness values.Testing
studioctl v0.1.0-preview.13.dotnet csharpier check src/Altinn.App.Api/Extensions/WebHostBuilderExtensions.cs src/Altinn.App.Api/Extensions/StudioctlLocalConfiguration.cs test/Altinn.App.Api.Tests/Extensions/WebHostBuilderExtensionsTests.csdotnet test test/Altinn.App.Api.Tests/Altinn.App.Api.Tests.csproj --filter "FullyQualifiedName~WebHostBuilderExtensionsTests" -v minimaldotnet build solutions/All.sln -v minimalstudioctl run -p /data/home/code/apps/martinotest-app-lib-prstarted the app on a random host port and routed throughhttp://local.altinn.cloud:8000/ttd/martinotest/.dotnet run --project App/App.csproj --launch-profile AppRef --no-buildimported studioctl config, bound a random host port, and was discoverable throughstudioctl app ps.Integration test note
I also reproduced a PDF integration failure locally, but it reproduces the same way on clean
upstream/mainat3c666448.Command:
Result on both this branch and clean upstream main: the app receives a 500 from
localtest-pdf3after about 30 seconds. PDF container logs show Chromium failing to load frontend CDN assets withERR_CERT_AUTHORITY_INVALID, then timing out waiting for#readyForPrint: