Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OVH: Allow ovh provider to connect to other endpoints than EU (#2625) #2651

Merged

Conversation

masterzen
Copy link
Contributor

Fix for #2625, allowing users to set OVH provider endpoint configuration to:

  • eu (default) to target the EU API endpoint
  • ca to target the Canada API endpoint
  • us to target the US API endpoint
  • any other url

If omitted, the default is the EU endpoint for backward compatibility.

…ge#2625)

This introduces the `endpoint` provider configuration parameter.
If not provided the provider will connect to the EU region for
backward compatibility.
The `endpoint` can be set to `eu`, `us` or `ca` depending on the OVH
region the use wants to manage domains and zones in.
It can also be set to any arbitrary URL for future OVH regions.
When all corrections are non modifying corrections (ie report only), we
don't need to add the REFRESH ZONE correction.
This was making some of the IGNORE integration test failed because the
test system was checking for 0 corrections applied.
@masterzen masterzen force-pushed the masterzen/2625-ovh-endpoint-config branch from fab1fad to 19d8d6a Compare November 27, 2023 18:40
@tlimoncelli tlimoncelli changed the title Allow ovh provider to connect to other endpoints than EU (#2625) OVH: Allow ovh provider to connect to other endpoints than EU (#2625) Nov 27, 2023
@tlimoncelli
Copy link
Contributor

Thanks!

@tlimoncelli
Copy link
Contributor

P.S. Thank you for a great PR. This is great! It fixes a real problem, has tests, and you updated the docs! I wish all PRs would be so complete! Thanks again!

@tlimoncelli tlimoncelli merged commit 69fb3b2 into StackExchange:master Nov 27, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants