You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an azuread_application resource where I'm using password. I'm using a time_rotate resource to managed the password's start_date and end_date, similar to the example in the documentation.
I now modified the application's redirect_uris, and in the terraform output I see that redirect_uris will be updated, as well as the password. It shows that the password will be deleted (-) and created (+). Note: the password's end_date still lies in the future. The password is created with the same start_date as before, which lies in the past. This results in an error in the terraform apply:
KeyCredentialsInvalidStartDate: Key credential start date is invalid.
I don't understand what the expected behavior should be.
Should a change to redirect_uris also recreate the password?
Is a password's start_date in the past allowed at the time of the password creation?
If the answers to 1. is "yes" and 2 is "no", then it looks like time_rotating isn't a solution to managed the password's dates, since whenever there is a change to a field that also recreates the password, we encounter the above error.
The text was updated successfully, but these errors were encountered:
I have an
azuread_application
resource where I'm usingpassword
. I'm using atime_rotate
resource to managed the password'sstart_date
andend_date
, similar to the example in the documentation.I now modified the application's
redirect_uris
, and in the terraform output I see thatredirect_uris
will be updated, as well as thepassword
. It shows that thepassword
will be deleted (-
) and created (+
). Note: the password'send_date
still lies in the future. The password is created with the samestart_date
as before, which lies in the past. This results in an error in theterraform apply
:I don't understand what the expected behavior should be.
redirect_uris
also recreate thepassword
?start_date
in the past allowed at the time of the password creation?time_rotating
isn't a solution to managed the password's dates, since whenever there is a change to a field that also recreates the password, we encounter the above error.The text was updated successfully, but these errors were encountered: