feat: add Ionos DNS Provider#13024
Open
andrexlenx wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it?
What this PR does:
Why we need it:
Currently, users who manage their domains through Ionos or Ionos Cloud cannot automate their SSL certificate provisioning through the platform.
Summary of your change
Backend: New DNS Provider Support
ionosandionoscloudproviders inagent/utils/ssl/dns_provider.go, including new handling for their credentials and API parameters. [1] [2]DnsTypeenum to includeIonosandIonosCloud.APIPrefixfield to theDNSParamstruct to support Ionos API credential requirements.Frontend: UI and Validation Updates
IonosandIonos Cloudto the selectable DNS types in the frontend (frontend/src/global/mimetype.ts).apiPrefix,apiSecret) and Ionos Cloud (token), including validation rules for these new fields. [1] [2]Please indicate you've done the following:
and opened a new docs issue or PR with docs changes if needed.