Skip to content
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

data variables must be four parts: data.TYPE.NAME.ATTR in: ${data.external.script} #37

Closed
ghost opened this issue Jul 16, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Jul 16, 2019

This issue was originally opened by @JasonOliverEmaze as hashicorp/terraform#20586. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.11.11 + provider.external v1.0.0

Terraform Configuration Files

  program = ["python", "${path.module}/secret.py", "-id", "SFTP-Key", "-keyname", "private-key"]
}

output "Private Key" {
  value = "${data.external.script}"
}

Expected Behavior

I am hoping for the script to output the variable as it would be if the python script was run (stdout).

Actual Behavior

I believe I need to include an attribute such as ${data.external.script.*}, ${data.external.script.all}, etc.?

`Error: Error loading C:\Users\oliverj\Documents\Code\github\test\test.tf: Error reading config for output Private Key: data.external.script: data variables must be four parts: data.TYPE.NAME.ATTR in:

${data.external.script}`

Steps to Reproduce

  1. terraform init
  2. terraform plan or terraform apply

References

@kmoe
Copy link
Member

kmoe commented Jul 1, 2021

It looks like the debugging attempts in hashicorp/terraform#20586 were going in the right direction. If the advice given there doesn't help, please reopen this issue including a valid Terraform config file and the Python script needed for a minimal reproduction.

@kmoe kmoe closed this as completed Jul 1, 2021
Copy link
Contributor

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant