Add configValidation to DattoRMM plugin

[TimWheeler-SQUP]

📋 Summary

Adds a configValidation.json to the DattoRMM plugin so users get a connection test step during plugin setup. It validates the Base URL, API Key, and API Secret by exercising the existing importSites data stream (calls api/v2/account/sites).

---

🔗 Related issue(s)

---

🧩 Plugin details

• Plugin name: Datto RMM
• Type of change:
  • Bug fix
  • New datastream
  • Enhancement to existing datastream
  • Performance improvement
  • Documentation / metadata / logo
  • Other (please describe): Adds configValidation step

---

⚠️ Breaking changes

Does this PR introduce any breaking changes?

• No
• Yes (please describe):

---

📚 Documentation

• No documentation changes needed

---

✅ Checklist

• No secrets or credentials included
• Plugin, datastream and UI naming follow SquaredUp guidelines
• I agree to the Code of Conduct

[clarkd]

Claude should flag this too but you'll need to bump the version number - otherwise looks good!

[clarkd]

@claude review this

[github-actions]

🧩 Plugin PR Summary

📦 Modified Plugins

• plugins/DattoRMM/v1

📋 Results

Step	Status
Validation	✅ Passed
Deployment	🚀 Deployed

🔍 Validation Details

✅ datto-rmm

{
  "valid": true,
  "pluginName": "datto-rmm",
  "pluginType": "cloud",
  "summary": {
    "Data Streams": 4,
    "Import Definitions": 1,
    "UI Configuration": true,
    "Has Icon": true,
    "Has Default Content": true,
    "Config Validation": true,
    "Custom Types": true
  }
}

[claude]

Version bump has been applied addressing my previous feedback — straightforward addition of a configValidation step.

Extended reasoning...

Overview

This PR adds a single configValidation.json file to the DattoRMM plugin and bumps the version in metadata.json from 1.0.1 to 1.0.2. The validation step reuses the existing importSites data stream to test connectivity during plugin setup. Total diff is ~12 lines.

Security risks

None. No credentials, secrets, or auth changes. The configValidation uses an existing data stream that already handles auth via the established OAuth2 flow defined in metadata.json. No new endpoints or attack surface.

Level of scrutiny

Low. This is exactly the kind of mechanical, pattern-following change that doesn't need human review: a small JSON file that follows the established configValidation pattern used by other plugins in the repo, plus a patch-level version bump. The schema is correct (steps array with displayName, dataStream, success, error, required fields).

Other factors

My previous review on 2026-05-12 flagged the missing version bump. The author has now addressed that feedback (1.0.1 → 1.0.2). CI validation passed (Config Validation: true in the bot summary). No outstanding reviewer comments remain unaddressed.