Skip to content

TF agent error in logs: "remote package address may not have a sub-path" #564

New issue

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

Closed
1 task done
danielllek opened this issue May 8, 2025 · 2 comments
Closed
1 task done

Comments

@danielllek
Copy link

Description

I run terraform enterprise (self-hosted tf cloud) and I see error in logs of TF agent when using iam-account submodule:
2025-05-07T12:28:36.198Z [ERROR] terraform: Failed to parse source address: registry.terraform.io/terraform-aws-modules/iam/aws//modules/iam-account: error="remote package address may not have a sub-path"

This error doesn't prevent successful plan/apply run, just annoys on log analysis.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version 4.4.0:

  • Terraform version:
    Terraform v1.8.5

  • Provider version(s):
    Terraform v1.8.5

Reproduction Code [Required]

My tf code is:

module "account" {
  source = "[email protected]:..my-repo-with-modules...//setup/account?ref=..."

And inside my module I invoke iam-account module

module "iam_account" {
  source  = "terraform-aws-modules/iam/aws//modules/iam-account"
  version = "4.4.0"
...

Steps to reproduce the behavior:

I'm using workspaces.

I've cleared cache.

Every run (plan/apply) of above code.

Expected behavior

Shouldn't be producing any error in tf logs

Actual behavior

Plan and apply work properly, but error is produced in TF agent logs.

Terminal Output Screenshot(s)

$ terraform plan
Running plan in the remote backend. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

The remote workspace is configured to work with configuration at
<workspace> relative to the target repository.

....

Waiting for the plan to start...

Terraform v1.8.5
on linux_amd64
Initializing plugins and modules...
... modules downloads ...

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

------------------------------------------------------------------------

Cost estimation:

Waiting for cost estimate to complete...

Cost estimation:

Resources: 0 of 12 estimated
           $0.0/mo +$0.0

Additional context

@bryantbiggs
Copy link
Member

this is not a module issue - this is a question for Hashicorp

@danielllek
Copy link
Author

Just thought maybe usage example in docs is wrong, thx.

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

No branches or pull requests

2 participants