duplicate azuread_application resources are created when redeploying

[diirib]

When creating an azuread_application resource, we define the display name. If we try to redeploy the same resource, since the applicationId is created automatically and is different from the one deployed the first time, terraform creates a new application with the same name but a different applicationId.

I would expect to at least have a parameter to specify if I want a new resource to be created or I'm just redeploying.

Is the applicationId the only way to check if there's an existing application?

[katbyte]

Hi @diirib,

Unfortunately the API works on GUID IDs. For now you can import the application via the app ID. In the future we could add a flag check_name_availiblity/prevent_duplicate_names which checks if the name is in use during creation and fails if it is.

[ghost]

This has been released in version 0.11.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 "azuread" {
    version = "~> 0.11.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 👉 [email protected]. Thanks!