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.

Sign up for GitHub

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

Jump to bottom

allow customer table to be specified instead of hard coded to "zones" #14

Open
mrjones-plip opened this issue Aug 6, 2018 · 0 comments
Open

allow customer table to be specified instead of hard coded to "zones" #14

mrjones-plip opened this issue Aug 6, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@mrjones-plip
Copy link
Contributor

Right now you can define your db connection in dnsauth.toml like this:

customer-db = "root:pass@(127.0.0.1)/customers"

However, the table inside this DB is hard coded to zones. We should make this so that dnsauth.toml can override what table the customers are found in
@mrjones-plip mrjones-plip added the enhancement New feature or request label Aug 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mrjones-plip