Fix import of stream analytics jobs that have been created via Azure Portal

[r0bnet]

Hey,

i found out that importing an existing Stream Analytics job that was created via the Portal didn't work. The reason was that a transformation object has a name property. It's used to read & update the transformation. Unfortunately it was called Transformation in this provider but Azure calls it main when you create the job in the portal.

In this PR i changed the name to be also main. In order to keep backward compatibility i'm reading the name of the transformation before updating it.

I tested the following:

• Create a Job via Portal
  • Import it via TF (with PR changes)
  • Update it via TF (with PR changes)
• Create a Job via the current 1.41.0 version of the provider
  • Import it via TF (with PR changes)
  • Update it via TF (with PR changes)

All tests completed without any error.

I also ran all acc tests for this resource successfully.

If you want me to add any further tests pls let me know.

[tombuildsstuff]

LGTM 👍

dismissing since changes have been pushed

[tombuildsstuff]

Tests pass:

[ghost]

This has been released in version 1.44.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.44.0"
}
# ... other configuration ...

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!