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

Imported DNS access does not trigger modifications when setting is empty #31

Closed
gmichels opened this issue Apr 5, 2023 · 0 comments · Fixed by #33
Closed

Imported DNS access does not trigger modifications when setting is empty #31

gmichels opened this issue Apr 5, 2023 · 0 comments · Fixed by #33
Assignees
Labels
bug Something isn't working

Comments

@gmichels
Copy link
Owner

gmichels commented Apr 5, 2023

Given the pre-populated DNS allowed list in ADG:

client1
client2
client3

When importing the resource with the bare-minimum configuration:

resource "adguard_dns_access" "test" {
}

A subsequent terraform plan does not trigger a modification of the allow list as expected.

$ terraform plan -target=adguard_dns_access.test
adguard_dns_access.external: Refreshing state... [id=1]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.

Provider should empty the allowed list as nothing is declared.

@gmichels gmichels added the bug Something isn't working label Apr 5, 2023
@gmichels gmichels self-assigned this Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant