modify application-test.yml in backend from refarch

[udobrmuc]

Pull Request

Changes

• ...
• ...

Reference

Issue: #XXX

Checklist

Note: If some checklist items are not relevant for your PR, just remove them.

General

• Added meaningful PR title and list of changes in the description

Summary by CodeRabbit

• Chores
  • Updated configuration property names for improved clarity in test settings. No changes to values or functionality.

[coderabbitai]

Walkthrough

The application-test.yml configuration file was updated by renaming two keys under the spring.security section: requestLogging became logging-mode, and userInfoUri became user-info-uri. The values associated with these keys remain unchanged.

Changes

File(s)	Change Summary
ehrenamt-justiz-backend/src/test/resources/application-test.yml	Renamed two configuration keys under spring.security section

Poem

In the meadow of YAML, keys took a new name,
"requestLogging" hopped to "logging-mode"—not quite the same!
"userInfoUri" stretched out, now "user-info-uri" in sight,
The values stayed cozy, tucked in just right.
A rabbit’s delight: neat configs tonight! 🥕

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5c9ac59 and 6287160.

📒 Files selected for processing (1)

• ehrenamt-justiz-backend/src/test/resources/application-test.yml (1 hunks)

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

• GitHub Check: build (ehrenamt-justiz-backend)

🔇 Additional comments (1)

ehrenamt-justiz-backend/src/test/resources/application-test.yml (1)

6-10: Confirmed: security prefix is correctly bound

• SecurityProperties.java is annotated with @ConfigurationProperties(prefix = "security").
• Application is annotated with @ConfigurationPropertiesScan, so the new prefix will be picked up.
• No remaining references or placeholders use the old spring.security.* keys.

No further changes required.

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 sequence diagram to generate a sequence diagram of the changes in 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.