IPL-9014 Support name and provider when unconventional display identifier

[jillirami]

Description

This pull request enhances support for creating Terraform registry modules from monorepos that do not follow the standard terraform-<provider>-<name> naming convention. It introduces optional fields for explicitly specifying the module name and provider, and adds comprehensive integration tests to ensure these scenarios work as expected.

Enhancements to module creation API:

• Added optional Name and Provider fields to the RegistryModuleCreateWithVCSConnectionOptions struct, allowing users to specify these values explicitly when creating modules from monorepos or repositories with non-standard names. This is particularly useful when using the source_directory option and the repository name does not follow the expected convention.

Testing improvements:

• Added a new integration test TestRegistryModulesCreateMonorepoNonStandardName in registry_module_integration_test.go to verify module creation with explicit Name and Provider in various monorepo scenarios, including:
  • Tag-based and branch-based module registration with non-standard repo names.
  • Deeply nested module paths.
  • Modules for different providers (e.g., azurerm, random).

Testing plan

E2E and written tests.

External links

• JIRA
• Related PR | Related PR#2
• Related JIRA

Output from tests

Including output from tests may require access to a TFE instance. Ignore this section if you have no environment to test against.

$ TFE_ADDRESS="https://example" TFE_TOKEN="example" go test ./... -v -run TestFunctionsAffectedByChange

jillianne.ramirez@jillianne go-tfe % TFE_ADDRESS="https://tfcdev-.ngrok.io/" TFE_TOKEN="" TF_ACC=1 ENABLE_BETA=1 GITHUB_REGISTRY_MODULE_IDENTIFIER="jillirami/terraform-null-mod-monorepo" OAUTH_CLIENT_GITHUB_TOKEN="ghp_" go test -v -run TestRegistryModulesCreateMonorepoNonStandardName -timeout 10m

Rollback Plan

Changes to Security Controls

[datadog-terraform-cloud-hashicorp]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 67b3b83 | Docs | Was this helpful? Give us feedback!}

[hashimoon]

Not sure how Atlas handles these use-cases, but I could see it being useful to also add unit tests there to ensure that the module and provider names are not transformed or standardized as they make there way through the app.

[github-actions]

Reminder to the contributor that merged this PR: if your changes have added important functionality or fixed a relevant bug, open a follow-up PR to update CHANGELOG.md with a note on your changes.