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

Leaving azurerm_kubernetes_cluster ssh_key key_data blank causes a terraform crash #903

Closed
katbyte opened this issue Feb 28, 2018 · 1 comment · Fixed by #904
Closed

Comments

@katbyte
Copy link
Collaborator

katbyte commented Feb 28, 2018

Terraform Version

Terraform v0.11.3
+ provider.azurerm (unversioned)
+ provider.random v1.1.0

Affected Resource(s)

  • terraform-provider-azurerm

Terraform Configuration Files

#from example
resource "azurerm_kubernetes_cluster" "aks_container" {
    name        = "akc-${random_integer.random_int.result}"
    location    = "${var.resource_group_location}"
    dns_prefix  = "akc-${random_integer.random_int.result}"

    resource_group_name = "${azurerm_resource_group.akc-rg.name}"
    kubernetes_version  = "1.8.7"


    linux_profile {
        admin_username = "${var.linux_admin_username}"
        ssh_key {
            key_data = ""
        }
    }

    agent_pool_profile {
        name        = "agentpool"
        count       = "2"
        vm_size     = "Standard_DS2_v2"
        os_type     = "Linux"
    }

    service_principal {
        client_id     = "${var.client_id}"
        client_secret = "${var.client_secret}"
    }
}

Debug Output

https://gist.github.com/katbyte/102cc21b01c10901386e1b564cfd17ab

Panic Output

https://gist.github.com/katbyte/102cc21b01c10901386e1b564cfd17ab

Expected Behavior

A graceful failure.

Actual Behavior

Terraform actually crashed.

Steps to Reproduce

Leave the ssh_key data blank

Important Factoids

no

References

@ghost
Copy link

ghost commented Mar 31, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants