Repository navigation
Add Neon Object Storage to destination constants - #5562
rishi-raj-jain wants to merge 1 commit into
Conversation
| name: "Minio Object Storage", | ||
| }, | ||
| { | ||
| key: "Neon", |
There was a problem hiding this comment.
Neon choice uses generic settings
Selecting Neon Object Storage sends Neon to rclone as --s3-provider=Neon. Rclone does not recognize that provider name, so it warns and uses generic S3 settings instead. Map this choice to Other until rclone supports Neon, so the saved setting matches what users get.
Knowledge Base Used: Backups and restore
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
No actionable findings. The earlier concern is overstated: rclone added Neon as a provider in v1.76.0. Older versions fall back to the generic Other provider with a warning, rather than failing, and Dokploy already passes --s3-force-path-style, which Neon requires. The added dropdown entry is therefore compatible with both current and older rclone versions.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
|
I see, I'll re open it once https://github.com/rclone/rclone/pull/10007/changes is merged. |
|
Neon is now a first party integration in rclone. |
What is this PR about?
Adds Neon Object Storage to one of the S3 destinations.
Disclaimer: I work as a contractor for Neon.
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
Screenshots (if applicable)


Confidence Score: 5/5
The PR appears safe to merge, with the existing non-blocking concern about rclone receiving `Neon` unchanged.Summary
Adds Neon Object Storage to the destination dropdown.
Reviews (2) · Last reviewed commit: "Add Neon Object Storage to destination c..." · Reviewed by Greptile