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

[dns-delegated] Some options should be per-domain, not per-component #654

Open
Nuru opened this issue May 3, 2023 · 0 comments
Open

[dns-delegated] Some options should be per-domain, not per-component #654

Nuru opened this issue May 3, 2023 · 0 comments

Comments

@Nuru
Copy link
Sponsor Contributor

Nuru commented May 3, 2023

In the dns-delegated component, arguments like dns_private_zone_enabled and certificate_authority_enabled should be set individually per domain, instead of per component and shared by all domains (as they currently are) so that public and private domains can be configured in the same component.

In Cloud Posse's convention-over-configuration usage, the reference architecture expect there to be one and only one dns-delegated component and for it to have that name. Having multiple dns-delegated components is not easy to deal with and should not be needed.

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

No branches or pull requests

1 participant