search

splunk / terraform-provider-synthetics

TF Provider for Splunk Synthetics
Apache License 2.0
4 stars 15 forks source link

Terraform Synthetics not showing step changes #38

Open aport1996 opened 10 months ago

aport1996 commented 10 months ago

create_http_check_screen

Hello,

As per the attached screenshot, we're having an issue with the Synthetics Terraform provider.

Basically, when we modify an existing step, instead of showing us the differences, as you can see from the screenshot, it will simply show that it will replace the step with the new values. This is an inconvenience because it's much more difficult this way to understand what you changed / what is changing.

Is it possible to change the behavior to show only the changes instead of a full recreation of the step block?

Many thanks!

greatestusername-splunk commented 9 months ago

Thanks for reporting this! Looks like this is roughly similar to https://github.com/splunk/terraform-provider-synthetics/issues/21 where you'd like to see a "changed" section rather than an output for the full resource with changes?

Just to clarify, what would you like to see? Do you have an example of such from another provider? That could be helpful in getting closer to a resolution for this issue.

Thanks!

aport1996 commented 9 months ago

Hello!

I believe that my request is indeed in line with wanting to see a "changed" section similar to issue #21. What I am looking for is a diff-like output where only the properties that have been updated are displayed, showing the transition from old value to new value. This would greatly simplify the review process by focusing on the modifications rather than the entire configuration block.

As an example, many version control systems provide a diff output that highlights only the changed lines. Similarly, some Terraform providers have a more granular output for plan/apply operations, which isolates the changes rather than displaying the complete configuration.

I believe this would enhance the usability of the Synthetics Terraform provider by making it easier to track and understand configuration changes.

Find below an example from the azure provider, related to the change of version for a Windows-based function app:

module.NAME.azurerm_windows_function_app.FUNCTION will be updated in-place ~ resource "azurerm_windows_function_app" "FUNCTION" { ~ functions_extension_version = "~4" -> "~1" id = "/subscriptions/xxxx" name = "FUNCTION"

(29 unchanged attributes hidden)

    # (9 unchanged blocks hidden)
}

We're looking forward to a resolution that enhances the clarity of the output.

Thank you!

greatestusername-splunk commented 9 months ago

Thanks for that information! Great to have an instance of a provider with the behavior you're referencing when scoping for this work.

Appreciate you opening the issue and idea! Thank you!