Open Nowaker opened 3 years ago
Hi, I'm investigating this, because I have tested with the setting you provide, and the behaviour ocurs for both TF 0.13 and TF0.14. However, if both attributes are entered via CLI there is no problem. This makes me suspect the issue is not with provider it self, but rather with terraform executable and the way it parses attributes.
Are you using any other provider that has mutliple required attributes that you could test in the same way? i.e. configure some required attributes via tf files and some via CLI?
I actually haven't used Terraform for a long while so I don't remember if this behavior applies to other providers. Last I used, it worked, but it was before the big Terraform changes that happened around a year ago or so. If you could confirm it's a Terraform issue, we could report an issue in their issue tracker as this behavior is definitely not expected. :-)
Terraform Version
v0.14.2
Affected Resource(s)
All.
Terraform Configuration Files
Expected Behavior
When API key isn't defined (and therefore, Terraform asks for it interactively) but the PowerDNS server URL is defined in the configuration, the provider sees the server URL parameter and talks to it.
Actual Behavior