-
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
Issue #1635 #3595
Comments
I may have found my answer in hashicorp/terraform-provider-azuread#4. It appears there is a replication/retry/timing issue when creating applications and service principals. Two PRs have been merged and targeted for the 0.4.0 release of the azuread provider. If someone could confirm my findings that would be nice and giving an estimate when the 0.4.0 release will occur would be amazing! |
@kyle-winkelman it appears Github isn't auto-redirecting those issues, which is unfortunate - but yes they look to be the same underlying cause. That issue's been fixed by one of several PR's to handle the eventual consistencies in Azure Active Directory - so whilst I can't give a timeframe at this point, it's part of the 0.4.0 milestone which is mostly done :) Since this appears to have been resolved I'm going to close this issue for the moment. Thanks! |
Thank you for the confirmation! It's not just no auto-redirection, I even tried manually going through all issues and its like #1635 disappeared. |
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! |
I have a similar issue as #2332 but I am unable to identify the current state or any additional information as issue #1635 appears to not exist, even though it is referenced in many other issues. I apologize for not following the outlined issue template, but thought it would be pointless to duplicate #2332. I am just hoping for an understanding of the outcomes of #1635 and any steps I can take to avoid the issue.
The text was updated successfully, but these errors were encountered: