Skip to content

feat: allow user to specify domain in container labels in order to identify it#198

Merged
steveiliop56 merged 2 commits into
mainfrom
feat/app-label-domain
Jun 15, 2025
Merged

feat: allow user to specify domain in container labels in order to identify it#198
steveiliop56 merged 2 commits into
mainfrom
feat/app-label-domain

Conversation

@steveiliop56
Copy link
Copy Markdown
Member

@steveiliop56 steveiliop56 commented Jun 15, 2025

Summary by CodeRabbit

  • New Features

    • Added support for handling and retrieving a domain label from container metadata.
  • Bug Fixes

    • Improved error handling and logging when retrieving container labels, ensuring failures in one container do not interrupt processing of others.
  • Refactor

    • Updated label retrieval logic to match containers by either ID or domain, providing more flexible matching criteria.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 15, 2025

Warning

Rate limit exceeded

@steveiliop56 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 59 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 4e6372e and c9b609b.

📒 Files selected for processing (1)
  • internal/handlers/handlers.go (1 hunks)

Walkthrough

The changes update the label retrieval logic in the Docker integration by modifying the GetLabels method to accept both an id and a domain parameter, adjust its matching logic, and enhance logging. The Labels struct now includes a Domain field, and label decoding now also extracts the tinyauth.domain label.

Changes

File(s) Change Summary
internal/docker/docker.go GetLabels method now takes id and domain parameters, updates matching logic and logging.
internal/handlers/handlers.go Updates variable naming and changes GetLabels call to use both id and host as arguments.
internal/types/config.go Adds Domain field to the Labels struct.
internal/utils/utils.go Adds "tinyauth.domain" to the list of decoded label keys in GetLabels.

Sequence Diagram(s)

sequenceDiagram
    participant Handler
    participant Docker
    participant Utils

    Handler->>Docker: GetLabels(id, domain)
    Docker->>Docker: Log start, check connection
    Docker->>Docker: Iterate containers
    Docker->>Docker: Inspect container, log warnings if needed
    Docker->>Utils: utils.GetLabels(container.Labels)
    Utils-->>Docker: Labels (including Domain)
    Docker->>Docker: Match on id or domain
    Docker-->>Handler: Return labels if match, else empty
Loading

Possibly related PRs

Poem

A hop through the code, a leap through the logs,
Now labels know domains, not just names of dogs.
Two arguments enter, more context to find—
With Docker and labels now better aligned.
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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 docstrings to generate docstrings for this 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.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (3)
internal/types/config.go (1)

103-109: Consider adding a struct-tag for the new Domain field

Domain will be populated exclusively through paerser/parser.Decode, so a tag is not strictly required.
However, for consistency with the rest of the codebase (which widely relies on mapstructure / json tags) and to avoid surprises if the struct is re-used elsewhere, add an explicit tag, e.g.:

-	Domain  string
+	Domain  string `label:"domain"`

This makes the intent self-documented and prevents accidental mismatches if different decoding mechanisms are introduced later.

internal/utils/utils.go (1)

204-205: Redundant path segment in parser.Decode call

Adding "tinyauth.domain" keeps the pattern used for the other fields, so it works.
But note that the first argument "tinyauth" already covers all first-level keys below it.
Passing both "tinyauth" and "tinyauth.domain" is therefore redundant and slightly slows down the decoder.

-	err := parser.Decode(labels, &labelsParsed, "tinyauth", "tinyauth.users", "tinyauth.allowed", "tinyauth.headers", "tinyauth.domain", "tinyauth.oauth")
+	err := parser.Decode(labels, &labelsParsed, "tinyauth", "tinyauth.users", "tinyauth.allowed", "tinyauth.headers", "tinyauth.domain", "tinyauth.oauth") // keep for now, but "tinyauth.domain" could be dropped

No functional bug, but worth keeping in mind.

internal/docker/docker.go (1)

77-85: Repeated Ping on every request is expensive

DockerConnected() performs a network round-trip (/ping).
Executing it on every auth request adds latency and unnecessary load; connection state rarely changes mid-process.

Consider caching the result for a short TTL or performing the connectivity test once during startup.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3397e2a and 4e6372e.

📒 Files selected for processing (4)
  • internal/docker/docker.go (3 hunks)
  • internal/handlers/handlers.go (1 hunks)
  • internal/types/config.go (1 hunks)
  • internal/utils/utils.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
internal/handlers/handlers.go (2)
internal/docker/docker.go (1)
  • Docker (18-21)
internal/utils/utils.go (1)
  • GetLabels (199-214)
internal/docker/docker.go (2)
internal/utils/utils.go (1)
  • GetLabels (199-214)
internal/types/config.go (1)
  • Labels (103-109)

Comment thread internal/handlers/handlers.go
Comment thread internal/docker/docker.go
@steveiliop56 steveiliop56 merged commit aed29d2 into main Jun 15, 2025
6 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant