Skip to content

feat: expose provider dependencies on module details (#483)#529

Open
dennismdejong wants to merge 1 commit into
PacoVK:mainfrom
dennismdejong:fix/upstream-483-module-provider-dependencies
Open

feat: expose provider dependencies on module details (#483)#529
dennismdejong wants to merge 1 commit into
PacoVK:mainfrom
dennismdejong:fix/upstream-483-module-provider-dependencies

Conversation

@dennismdejong

Copy link
Copy Markdown

Fixes #483

Provider dependencies parsed by terraform-docs are now attached to the Module model and surfaced through the module API.

Changes:

  • Added providerDependencies field to Module.java with ModuleProviderDependency inner class
  • Added DynamoDB converter and schema entry for the new field
  • Implemented updateModuleProviderDependencies in all 3 backends (DynamoDB, CosmosDB, Elasticsearch)
  • Wired ReportListener to extract provider deps from terraform-docs output and persist them

Provider dependencies parsed by terraform-docs are now attached to the
Module model and surfaced through the module API. Added new field
providerDependencies to Module, updated DynamoDB/Elasticsearch/CosmosDB
backends, and wired ReportListener to extract and persist provider
dependencies after documentation generation.

Fixes PacoVK#483
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Providers hosted in Tapir are not listed as dependency on modules

1 participant