Containerize connector

[luisina-santos]

Summary by CodeRabbit

• Chores
  • Enforced required configuration for AccessTokenName, AccessTokenSecret, and ServerPath. These fields must now be explicitly set; missing values will trigger validation errors.
  • Users should verify their configuration includes these values to ensure successful startup and operation.
  • This change improves reliability by preventing incomplete configurations from being accepted.

[coderabbitai]

Walkthrough

The change updates validation in pkg/config/config.go by marking AccessTokenName, AccessTokenSecret, and ServerPath as required using field.WithRequired(true). No other identifiers or control flow were modified.

Changes

Cohort / File(s)	Summary
Config validation pkg/config/config.go	Added required validation via field.WithRequired(true) for AccessTokenName, AccessTokenSecret, and ServerPath; no other structural or control-flow changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I nibbled the configs, crisp and bright,
Marked three keys “must,” to set them right.
No wandering flows, no rabbit holes—
Just fields that hop to stricter roles.
Thump-thump! The tokens now stand tall,
Required carrots for one and all. 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title “Containerize connector” does not reflect the actual changes, which add required validation to specific configuration fields rather than any containerization logic.	Please update the pull request title to describe the addition of required validation on the AccessTokenName, AccessTokenSecret, and ServerPath configuration fields.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch luisinasantos/containerize-connector

---

📜 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 ad63751 and eaf4590.

⛔ Files ignored due to path filters (8)

• .github/workflows/capabilities_and_config.yaml is excluded by none and included by none
• .github/workflows/release.yaml is excluded by none and included by none
• .gon-amd64.json is excluded by none and included by none
• .gon-arm64.json is excluded by none and included by none
• .goreleaser.docker.yaml is excluded by none and included by none
• .goreleaser.yaml is excluded by none and included by none
• Dockerfile.lambda is excluded by none and included by none
• cmd/baton-tableau/main.go is excluded by none and included by none

📒 Files selected for processing (1)

• pkg/config/config.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Cursor Bugbot

🔇 Additional comments (3)

pkg/config/config.go (3)

8-13: Good call marking the token name as required.

This prevents silent misconfigs at runtime and aligns with the connector’s authentication expectations.

---

15-21: Requiring the token secret is spot-on.

It guarantees the secret must be provided up front, eliminating confusing “missing secret” failures later.

---

23-28: Making the server path mandatory is the right move.

Connection attempts can’t succeed without it, so surfacing the requirement during validation is ideal.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}