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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to disable IPv6 (create the A record but not the AAAA record in Route 53) #364

Closed
davehensley opened this issue Jul 12, 2020 · 1 comment

Comments

@davehensley
Copy link
Contributor

davehensley commented Jul 12, 2020

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Feature Request

Is your feature request related to a problem? Please describe.
Thank you for making this very useful plugin!

I have a situation where I need my endpoints to support IPv4 only, so I don't want to create an AAAA record in Route 53.

Describe the solution you'd like
I would like a new createRoute53IPv6Record option to be added, that works exactly like createRoute53Record (and similarly defaults to true), but can be overridden with false if I only want to support IPv4. (For backward compatibility, and because I can't imagine a situation where anyone would need to support IPv6 but not IPv4, neither record gets created if createRoute53Record is false.)

custom:
  customDomain:
    createRoute53IPv6Record: false

Describe alternatives you've considered
I suppose some alternatives would be to downgrade to version 3.1.0 of the plugin (before IPv6 support was added), or to disable createRoute53Record and create the DNS record manually.

Any Other Info
I have implemented this feature here: #365

@rddimon
Copy link
Collaborator

rddimon commented Feb 9, 2022

Hi @davehensley

We have released this option recently #480

Closing it but feel free to reopen in case of any related issues

@rddimon rddimon closed this as completed Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants