Update config schema changes for Salesforce opps to Google sheets integration

[hasathcharu]

$subject.

Summary by CodeRabbit

• Chores
  • Updated logging configuration schema with enhanced structure and flexibility.
  • Added support for multiple log destinations (console and file output).
  • Introduced configurable log formats and standardized log levels.
  • Added optional sensitive data masking capability for logs.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9958fa76-5430-4c20-843d-ef6278a9704b

📥 Commits

Reviewing files that changed from the base of the PR and between c72e2d4 and 38a1b53.

📒 Files selected for processing (1)

• ballerina-integrator/salesforceops-to-googlesheets/.choreo/config-schema.json

---

Walkthrough

Updated the logging configuration schema from version 2.9.0 to 2.14.0, introducing structured destination support, restricting level to an enum, adding format and enableSensitiveDataMasking options, and defining keyValues schema with constrained properties for enhanced logging capabilities.

Changes

Cohort / File(s)

Summary

Logging Schema Configuration ballerina-integrator/salesforceops-to-googlesheets/.choreo/config-schema.json

Updated ballerina.log schema from v2.9.0 to v2.14.0 with new destinations array supporting StandardDestination (stderr/stdout) and FileOutputDestination (with path/mode). Changed module log level from unrestricted string to enum (WARN|INFO|ERROR|DEBUG). Added format enum (logfmt|json), enableSensitiveDataMasking boolean, and keyValues with restricted properties (msg, error, stackTrace, module). Added top-level requiredLevel: 3.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 Logs now flow in structured streams,
Destinations guide like moonbeams,
Enums tame the wild string days,
Sensitive data masked in countless ways! ✨📋

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is incomplete, containing only '$subject.' instead of required template sections like Purpose, Goals, Approach, and other critical information.	Complete the description using the provided template, including Purpose, Goals, Approach, Release notes, and other applicable sections with meaningful content.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating a configuration schema for the Salesforce-to-Google Sheets integration, which matches the JSON schema modifications detailed in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

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