-
Notifications
You must be signed in to change notification settings - Fork 0
bug: referencing agent tuple in module throws confusing error #583
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
Comments
@stirby this is expected terraform behavior as |
I am moving this to internal as I agree with the expected behavior. But @Emyrk wanted to investigate why that was the resulting error. |
❌ Failed to start the workspace. Please check the action logs for details. |
@matifali Wait, if you reference a block that uses Can you link to the TF docs on that? |
@Emyrk I could not find any explicit docs on this, but this is my understanding from count in Terraform. I am not sure if I was able to explain this or made it more confusing. |
Is there an existing issue for this?
Current Behavior
This is likely a case where we need to improve docs/error message.
There's a strange indexing error that gets thrown when the
coder_agent
is assigned acount
and must be referenced with a tuple, but a module referencing it does contain acount
attribute.With the following agent and module definition...
Terraform throws the following error:
Unless you specify
count
in the module, then no error is thrown:Relevant Log Output
Expected Behavior
I did not realize that we had to define the count, so this may be a discoverability issue.
Steps to Reproduce
coder_agent
withcount = data.workspace.<me>.start_count
count = data.workspace.<me>.start_count
to module to resolve.Environment
The text was updated successfully, but these errors were encountered: