-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New Resource: azurerm_kusto_cluster_customer_managed_key
#7520
New Resource: azurerm_kusto_cluster_customer_managed_key
#7520
Conversation
azurerm_kusto_cluster_customer_managed_key
f3c9f84
to
14c7cc7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jrauschenbusch, taking a look through this resource, I have to say it seems better suited to just be used as an attribute on the existing cluster resource. I probably missing something so do you mind talking through a little of your thoughts around why this is split out into its own resource?
Hey @mbfrahry, there was a discussion with @tombuildsstuff that first the cluster needs to be created with an identity type |
@mbfrahry @tombuildsstuff If we could get this merged today, release 2.18.0 would contain all major Kusto Cluster features currently provided by the SDK. Especially for enterprise users custom encryption keys for encryption at rest are a must. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jrauschenbusch, I'm seeing errors when running the tests
TestAccAzureRMKustoClusterCustomerManagedKey_basic: testing.go:684: Step 0 error: errors during apply:
Error: Error retrieving Kusto Cluster "acctestkcun8z6" (Resource Group "acctestRG-200709182537441411"): `properties` was nil
I'm investigating more on my side but any help from your end would be appreciated too
@mbfrahry I'm currently facing the following problems when running the acc tests:
Maybe you have a quick idea of where they come from? |
So it looks like the import test is failing because we're calling |
The inconsistent results failure normally happens when what is in the config differs from what is being returned by the api. That one will require more digging into. Your best bet might be to see what is being returned by the api and compare it to what's in the config |
I'm building it locally now to see if I can help get to the bottom of it |
Hmmm, so I have a bit more information. We're definitely sending the key vault properties to the api but we're not getting them back and then looking in the portal they aren't there either. This is what we're sending with values removed:
And this is what we get back:
|
Another lead! So it looks like
Doing this in the portal returns the same error message |
Thanks for giving the hints. I'm going to fix it. |
Hey @mbfrahry Regarding the I've now tested a lot with the resource itself and with the Azure portal, and it seems that there is currently an issue on the Azure API. I'll file a bug ticket for it. |
Hey @mbfrahry Finally the Kusto product team has fixed the bug related to the Internal Server Error message. I've finally fixed some minor bugs within the resource implementation and acc tests and now it seems to look good. |
Acceptance tests succeed now 👍 make acctests SERVICE='kusto' TESTARGS='-run=TestAccAzureRMKustoClusterCustomerManagedKey' TESTTIMEOUT='60m'
==> Checking that code complies with gofmt requirements...
==> Checking that Custom Timeouts are used...
==> Checking that acceptance test packages are used...
TF_ACC=1 go test -v ./azurerm/internal/services/kusto/tests/ -run=TestAccAzureRMKustoClusterCustomerManagedKey -timeout 60m -ldflags="-X=github.com/terraform-providers/terraform-provider-azurerm/version.ProviderVersion=acc"
=== RUN TestAccAzureRMKustoClusterCustomerManagedKey_basic
=== PAUSE TestAccAzureRMKustoClusterCustomerManagedKey_basic
=== RUN TestAccAzureRMKustoClusterCustomerManagedKey_requiresImport
=== PAUSE TestAccAzureRMKustoClusterCustomerManagedKey_requiresImport
=== RUN TestAccAzureRMKustoClusterCustomerManagedKey_updateKey
=== PAUSE TestAccAzureRMKustoClusterCustomerManagedKey_updateKey
=== CONT TestAccAzureRMKustoClusterCustomerManagedKey_basic
=== CONT TestAccAzureRMKustoClusterCustomerManagedKey_updateKey
=== CONT TestAccAzureRMKustoClusterCustomerManagedKey_requiresImport
--- PASS: TestAccAzureRMKustoClusterCustomerManagedKey_basic (1584.25s)
--- PASS: TestAccAzureRMKustoClusterCustomerManagedKey_updateKey (1651.15s)
--- PASS: TestAccAzureRMKustoClusterCustomerManagedKey_requiresImport (1692.00s)
PASS
ok github.com/terraform-providers/terraform-provider-azurerm/azurerm/internal/services/kusto/tests 1693.087s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @jrauschenbusch!
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 👉 [email protected]. Thanks! |
Provides Kusto Cluster support for a customer managed encryption key