I saw that you commented on hashicorp/terraform#17018 so I would guess you're already aware, but I'm creating this issue for clarity, or so it can be closed WONTFIX
Expected Behavior
I would guess so long as the filenames don't clash, the plugin can distinguish its own schema files from terraform's schema files because they have differing top-level keys (yours ".schema_version", theirs "format_version"). I actually would presume that terraform's would win in the case of conflict, since it can be that a project is running with a custom build of the aws provider, for example, and would want those completion attributes and documentation over the pre-generated ones
Prerequisites
Installation details
Help->About->Copy to Clipboard
)Settings->Plugins
)terraform -v
)Related Links
This is related to #128, #131, hashicorp/terraform#20446 and is documented upstream as https://www.terraform.io/docs/commands/providers/schema.html#providers-schema-representation
I saw that you commented on hashicorp/terraform#17018 so I would guess you're already aware, but I'm creating this issue for clarity, or so it can be closed WONTFIX
Expected Behavior
I would guess so long as the filenames don't clash, the plugin can distinguish its own schema files from terraform's schema files because they have differing top-level keys (yours
".schema_version"
, theirs"format_version"
). I actually would presume that terraform's would win in the case of conflict, since it can be that a project is running with a custom build of theaws
provider, for example, and would want those completion attributes and documentation over the pre-generated onesthen the completion for the providers in use by the project would be available (subject to the IJ restart, as documented in the readme)
Actual Behavior
The custom provider attributes, data sources, and resources are not known