Add Optional OVH_ZONE Property to OVH DNS Provider
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
The OVH DNS provider currently does not allow specifying a specific DNS zone. This makes it difficult to use the same OVH credentials while restricting DNS operations to a particular zone. An optional OVH_ZONE property would support both use cases: managing all available zones or targeting a specific zone.
Describe the solution you'd like
Add an optional OVH_ZONE property to the OVH DNS provider configuration.
- If
OVH_ZONEis provided, use it to target the specified DNS zone. - If
OVH_ZONEis not provided, keep the current behavior and allow the credentials to be used across all available zones.
Describe alternatives you've considered
One alternative would be to create separate OVH DNS provider configurations or credentials for each DNS zone. However, this would add unnecessary configuration and credential management overhead.
Keeping OVH_ZONE optional provides a simpler solution while preserving the existing behavior for users who need access to multiple zones.
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the OVH DNS provider configuration and any existing handling of DNS zones. Trace how provider properties are read and how DNS operations select zones, then add coverage for both a specified OVH_ZONE and the current behavior when it is omitted. Done means a configured zone is targeted while existing multi-zone use remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100