fix: application insights requests

[mirkoSekulic]

Description

Moves registration of application insights before calling Scrutor Decorate method.

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)

Documentation

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

Summary by CodeRabbit

• Chores
  • Restored service configurations in the application's backend setup
  • Reintegrated previously removed service registrations
  • Maintained existing logging and configuration behaviors

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request involves modifications to the Program.cs file in the backend, specifically focusing on the ConfigureServices method. The changes primarily consist of re-adding previously removed service registrations, including HttpContextAccessor, MemoryCache, ResponseCompression, and HealthChecks. The restoration maintains the existing configuration logic and method structure, ensuring that the previous service setup is preserved without introducing new functionality.

Changes

File	Change Summary
backend/src/Designer/Program.cs	Restored service registration methods for HttpContextAccessor, MemoryCache, ResponseCompression, and HealthChecks in the ConfigureServices method

Possibly related PRs

• fix: build warning #14484: Documentation comment updates in SchemaModelService class, potentially related to service configuration context

Suggested labels

solution/platform, team/studio-core

Suggested reviewers

• JamalAlabdullah
• standeren

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d752ba and 83c99b0.

📒 Files selected for processing (1)

• backend/src/Designer/Program.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: Run dotnet build and test (macos-latest)
• GitHub Check: Build environment and run e2e test
• GitHub Check: Run dotnet build and test (windows-latest)
• GitHub Check: Run dotnet build and test (ubuntu-latest)
• GitHub Check: Analyze

🔇 Additional comments (3)

backend/src/Designer/Program.cs (3)

Line range hint 1-1: Please clarify the PR title "fix: application insights requests".

The existing Application Insights configuration appears correct and comprehensive. Could you provide more context about what specific Application Insights request issues this PR is addressing? This would help ensure the changes fully resolve the intended problem.

---

219-225: LGTM! Verify health check endpoint after deployment.

The re-added core services are essential for the application's functionality. Good to see them restored.

Run this script to verify the health check endpoint configuration:

✅ Verification successful

Health check implementation verified and properly configured

The health check is correctly implemented with:

• Basic health status reporting
• Proper endpoint mapping at /health
• Standard interface implementation

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify health check endpoint mapping and implementation

# Check if health check endpoint is mapped
rg -A 2 'MapHealthChecks\("/health"\)' 

# Verify health check implementation
ast-grep --pattern 'class HealthCheck : IHealthCheck {
  $$$
  Task<HealthCheckResult> CheckHealthAsync($_, $_) {
    $$$
  }
}'

Length of output: 384

---

Script:

#!/bin/bash
# Search for HealthCheck class definition and usage
rg -g '*.cs' 'class HealthCheck' -A 5

# Search for any file containing HealthCheck in its name
fd HealthCheck

# Try alternative ast-grep pattern for possible implementation variations
ast-grep --pattern 'class HealthCheck {
  $$$
}'

Length of output: 774

---

Script:

#!/bin/bash
# Get the complete implementation of HealthCheck class
cat backend/src/Designer/Health/HealthCheck.cs

Length of output: 719

---

228-237: LGTM! Verify authentication configuration.

The configuration methods are restored in the correct order, maintaining proper middleware pipeline setup.

Run this script to verify the authentication configuration:

✅ Verification successful

Authentication configuration verified and secure

The authentication setup follows security best practices with:

• Correct middleware ordering
• Secure cookie configuration
• Standard OpenID Connect implementation
• Proper handling of multiple authentication schemes

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify authentication configuration and middleware setup

# Check authentication configuration
rg -A 5 'ConfigureAuthentication\(' 

# Verify middleware order in Configure method
rg -A 10 'app\.UseAuthentication\(\);?\s+app\.UseAuthorization\(\);'

Length of output: 1176

---

Script:

#!/bin/bash
# Check AddGiteaOidcAuthentication implementation
ast-grep --pattern 'AddGiteaOidcAuthentication($_,$_,$_) {
  $$$
}'

# Look for Configure method and middleware setup with broader pattern
rg -A 15 'Configure\(.*app\s*,.*\)\s*\{' 

# Alternative middleware setup patterns
rg -A 10 'UseMiddleware|app\.Use'

Length of output: 3893

---

Script:

#!/bin/bash
# Check OIDC authentication setup
rg -A 15 'AddGiteaOidcAuthentication|\.AddOpenIdConnect'

Length of output: 6273

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.