-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Change DomainFilter to apply to records as well #1442
Change DomainFilter to apply to records as well #1442
Conversation
This moves `domain_filter.go` to the `endpoint` package to make it possible to filter and exclude record names in `plan.filterRecordsForPlan()` so it does not have to be implemented in every single provider. Because some providers access `DomainFilter.filters` directly it had to be exported.
Welcome @bl1nk! |
@bl1nk Highly appreciated change! Do you have a public docker image containing these changes somewhere? |
@alexanderbuhler Unfortunately not. With the only requirement being Docker installed and running you can clone the repo, check out my branch and run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bl1nk, linki The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@bl1nk Thank you! |
These changes were implemented for the setup mentioned in #1137:
domain_filter.go
was moved to theendpoint
package to make it possible to filter and exclude record names inplan.filterRecordsForPlan()
so it does not have to be implemented in every single provider. Now Process "2" will only create DNS entries forexample.com
. Before--exclude-domains
was only filtering/excluding DNS zones.Because some providers access
DomainFilter.filters
directly it had to be exported.A build with these changes has been running in production at FREE NOW for a couple of weeks without issues.
Fixes #1137