Fix: EU region URL change for NinjaOne plugin

[Deenk]

📋 Summary

Quite a simple region change for the EU region for the NinjaOne plugin. This does not break existing EU region customers as the new/changed URL resolves to the same API. This change is needed though as some NinjaOne customers do require eu.ninjarmm.com. The existing eu-api.ninjarmm.com URL that the plugin uses is an alias that seemingly not all customers can use.

---

🔗 Related issue(s)

https://squaredup-eng.atlassian.net/browse/PLUG-4662

---

🧩 Plugin details

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

---

⚠️ Breaking changes

Does this PR introduce any breaking changes?

• No
• Yes (please describe):

If yes, describe:

• What breaks
• Who is impacted
• Any migration steps

---

📚 Documentation

• Documentation updated
• 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

Summary by CodeRabbit

• Bug Fixes
  • Updated the NinjaOne API base URL settings to use the latest endpoint hostnames (including Canada and EU), ensuring requests go to the correct regional services.
• Chores
  • Bumped the NinjaOne plugin version to 1.1.14.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5850d391-96d5-4b20-ba39-cef4456fd50c

📥 Commits

Reviewing files that changed from the base of the PR and between 3717b12 and 9545570.

📒 Files selected for processing (2)

• plugins/NinjaOne/v1/metadata.json
• plugins/NinjaOne/v1/ui.json

---

📝 Walkthrough

Walkthrough

Updated NinjaOne regional API base URL hostnames in ui.json and incremented the plugin version from 1.1.12 to 1.1.14 in metadata.json.

Changes

NinjaOne endpoint and version update

Layer / File(s)	Summary
Endpoint configuration and version update plugins/NinjaOne/v1/ui.json, plugins/NinjaOne/v1/metadata.json	Regional apiBaseUrl option values and the default hostname are updated while labels remain unchanged; the plugin version is incremented to 1.1.14.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly reflects the main change: NinjaOne region URL updates, especially the EU endpoint change.
Description check	✅ Passed	The description is mostly complete and matches the template with summary, issue link, change type, breaking changes, docs, and checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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.}

[github-actions]

🧩 Plugin PR Summary

📦 Modified Plugins

• plugins/NinjaOne/v1

📋 Results

Step	Status
Validation	✅ Passed
Deployment	🚀 Deployed

🔍 Validation Details

✅ ninja-one

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

[clarkd]

Are we able to test this change with other regions or confident this will work as expected?

[vinbab]

Are we able to test this change with other regions or confident this will work as expected?

@Deenk @clarkd

• I'd change the title and description to reflect the change (all regions).
• We have 8 tenants in US and 5 in EU. I'd feel a lot more comfortable to approve if indeed we could confirm these two regions still work fine, for new and existing plugins.