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

Flow variables are not updated when changed in the flow import JSON #324

Closed
patrickcping opened this issue Jun 3, 2024 · 0 comments · Fixed by #325
Closed

Flow variables are not updated when changed in the flow import JSON #324

patrickcping opened this issue Jun 3, 2024 · 0 comments · Fixed by #325
Assignees
Labels
status/triaged The issue/PR has completed initial triage and needs assignment type/bug Something isn't working
Milestone

Comments

@patrickcping
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

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

v0.3.2

Terraform Version

v1.8.4

Affected Resource(s)

  • davinci_flow

Terraform Configuration Files

# Copy-paste your DaVinci related Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

# Remember to replace any account/customer sensitive information in the configuration before submitting the issue

# NOTE: PLEASE DO NOT share DaVinci JSON exports publicly without encrypting files first.  DaVinci JSON exports can contain environment/tenant specific information, and may also include secrets.

resource "davinci_connection" "my_awesome_flow_connector" {
  environment_id = var.environment_id

  name         = "Flow"
  connector_id = "flowConnector"
}

resource "davinci_flow" "my_awesome_subflow" {
  environment_id = var.environment_id

  name      = "My Awesome Subflow"
  flow_json = file("./path/to/example-subflow.json")

  connection_link {
    id                           = davinci_connection.my_awesome_flow_connector.id
    name                         = davinci_connection.my_awesome_flow_connector.name
    replace_import_connection_id = "3332************************1ea3"
  }
}

Debug Output

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to davinci_flow.nnzitpwmsp, provider "provider[\"registry.terraform.io/pingidentity/davinci\"]" produced an unexpected new value: .flow_variables: planned set element cty.ObjectVal(map[string]cty.Value{"context":cty.StringVal("flow"),
│ "description":cty.NullVal(cty.String), "flow_id":cty.StringVal("bd10***********************cf36"), "id":cty.StringVal("fdgdfgfdg##SK##flow##SK##bd10***********************cf36"), "max":cty.NumberIntVal(2000), "min":cty.NumberIntVal(0), "mutable":cty.True,
│ "name":cty.StringVal("fdgdfgfdg"), "type":cty.StringVal("property")}) does not correlate with any element in actual.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Panic Output

N/a

Expected Behavior

Variables should be updated in DaVinci

Actual Behavior

Variables are not updated in DaVinci, leading to broken flow

Steps to Reproduce

  1. terraform apply
  2. Add a new variable / delete a variable / modify a variable in the flow export JSON example-subflow.json
  3. terraform apply

Important Factoids

References

None

@patrickcping patrickcping added type/bug Something isn't working status/triaged The issue/PR has completed initial triage and needs assignment labels Jun 3, 2024
@patrickcping patrickcping added this to the v0.3.3 milestone Jun 3, 2024
@patrickcping patrickcping self-assigned this Jun 3, 2024
@patrickcping patrickcping linked a pull request Jun 3, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triaged The issue/PR has completed initial triage and needs assignment type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant