fix(source-vitally): add missing airbyte_secret flag to secret_token spec field#81345
fix(source-vitally): add missing airbyte_secret flag to secret_token spec field#81345devin-ai-integration[bot] wants to merge 3 commits into
Conversation
…spec field Co-Authored-By: bot_apk <apk@cognition.ai>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
Co-Authored-By: bot_apk <apk@cognition.ai>
Co-Authored-By: bot_apk <apk@cognition.ai>
|
|
Deploy preview for airbyte-docs ready!
Deployed with vercel-action |
|
↪️ Triggering Reason: Draft PR with CI passing (1 unrelated failure), linked to P3 oncall issue. Ready for prove-fix validation. |
|
|
🟢 Fix Proven — No Regression Detected SummaryThe addition of Pre-flight Checks
Regression Test ResultsPre-release version:
Attempt 4 — Detailed READ Comparison
Both versions: Evidence Assessment
Workflow Links
Detailed results with connection context available in the linked oncall issue. |
|
|
↪️ Triggering Reason: Prove-fix completed (🟢 Fix Proven — No Regression Detected). Advancing to AI review. |
Reviewing PR for connector safety and quality.
|
🛡️ AI PR Review Report🟢 Review Action: APPROVEDAll 12 gates passed. 🟦 Risk Level: 1/5Adding 📋 PR DetailsConnector(s): 🔍 Gate Evaluation DetailsGate-by-Gate Analysis
Detailed Gate NotesCI Checks: The Live / E2E Tests: The
Code Security: The diff adds Backwards Compatibility: No spec comparison needed — the only manifest.yaml change is adding 📚 Evidence ConsultedEvidence
|
|
↪️ Triggering Reason: AI review approved (APPROVE). Advancing to final readiness stage. |
Auto-merge evaluation: FAILPreconditions (all must pass)
Change scope (at least one must pass)❌ No matching change scope detected. |
What
Resolves https://github.com/airbytehq/oncall/issues/13021:
The
secret_tokenfield in source-vitally's spec is missingairbyte_secret: true. This was introduced in #53648 which rewrote the spec — the oldapi_keyfield had the flag, butsecret_tokenlost it whilebasic_auth_headerkept it.Without this flag, the secret token value is displayed in plaintext in the UI and logs.
How
Added
airbyte_secret: trueto thesecret_tokenproperty inmanifest.yaml, matching the pattern already used bybasic_auth_header.Declarative-First Evaluation
This is a one-line YAML property addition to the connector spec — no custom components needed or evaluated.
Test Coverage
Added
unit_tests/test_manifest.pythat parses the manifest YAML and asserts bothsecret_tokenandbasic_auth_headerhaveairbyte_secret: true.Review guide
airbyte-integrations/connectors/source-vitally/manifest.yaml— single line additionairbyte-integrations/connectors/source-vitally/unit_tests/test_manifest.py— new test fileairbyte-integrations/connectors/source-vitally/metadata.yaml— version bump 0.4.3 → 0.4.4docs/integrations/sources/vitally.md— changelog entryUser Impact
Secret token values will now be masked in the Airbyte UI and logs, preventing accidental exposure of credentials.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/df91f844f8f648e29ef46bf82ee50345