We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Trying to use #https://registry.terraform.io/providers/logicmonitor/logicmonitor/latest/docs/resources/datasource#collector_attribute as an example of datasource results in error. Please update documentation / resource code. Error in vscode Required attribute "collector_attribute" not specified: An attribute named "collector_attribute" is required hereTe
Required attribute "collector_attribute" not specified: An attribute named "collector_attribute" is required hereTe
The text was updated successfully, but these errors were encountered:
Hi @AntonSynchrofazatron , Can you please recheck the TF plan , as collector attribute needs to be specified in the TF configuration. Please check the example usage: https://registry.terraform.io/providers/logicmonitor/logicmonitor/latest/docs/resources/datasource#collector_attribute
Sorry, something went wrong.
hello @lm-madhvi i mean the provided resource example is misleading and throughs an error immediately when added to a code. eg
it allows to run plan with collector_attribute = [{ name = "jdbc" }]
collector_attribute = [{ name = "jdbc" }]
but still validation of the resource looks bad...
Hi @AntonSynchrofazatron , We are working on the fix for this.
No branches or pull requests
Trying to use #https://registry.terraform.io/providers/logicmonitor/logicmonitor/latest/docs/resources/datasource#collector_attribute
as an example of datasource results in error. Please update documentation / resource code.
Error in vscode
Required attribute "collector_attribute" not specified: An attribute named "collector_attribute" is required hereTe
The text was updated successfully, but these errors were encountered: