Skip to content

Examples leveraging submodules have relative paths to directories inside of the project instead of referencing Terraform Registry Module path #175

@thogarty

Description

@thogarty

The module source is relative in the examples.

E.g.

module "create_virtual_device_2_azure_connection" {
  source = "../../modules/virtual-device-connection"
  ...
}

Instead of being a reference to the published module in the Terraform Registry:

module "create_virtual_device_2_azure_connection" {
  source  = "equinix/fabric/equinix//modules/virtual-device-connection"
  version = "0.18.0"
  ...
}

This means that we are not showing customers how to leverage the module fully and are omitting an important step.

Similar issue to #144

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions