-
Notifications
You must be signed in to change notification settings - Fork 1
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
[BUG] Long flow names cause a panic during plan/apply #230
Comments
fixing name doesn't fix this. There is something else afoot but I'm not posting the JSON flow on Github |
It looks like a missing version was the culprit.
I suspect it needs a value check in the routine somewhere? |
@dbryar thanks for opening this, I included handling for the issue in the latest (v0.2.0) release. Note, to use the latest release there is a small config update required. |
@samir-gandhi I believe this bug has been reintroduced in v0.3.0 The previous version shows
And in v0.3.0 we had a fairly lengthy investigation trying to work out this error, until rolling back
|
@dbryar thank you for bringing this up, I've added the triage label as we look into it |
I've done a lot more research/debugging; opened a new ticket |
Resuming the thread on #289 , we'll leave this ticket closed |
Community Note
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
DaVinci Terraform provider Version
0.1.13
Terraform Version
1.4.2
Affected Resource(s)
davinci_flow
Terraform Configuration Files
N/A
Panic Output
Expected Behavior
Should apply terraform plan
Actual Behavior
It crashed
Steps to Reproduce
terraform apply
Important Factoids
The flow refused to import in to DaVinci console until I reduced the length of the flow name. Not sure if this is the only reason for the crash, however it seems that a flow/subflow with a long/descriptive name causes a panic
The text was updated successfully, but these errors were encountered: