-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Add support for creating Managed Microsoft Active Directory and Directory Connectors in AWS #4388
Add support for creating Managed Microsoft Active Directory and Directory Connectors in AWS #4388
Conversation
As an aside, are there downsides to marking these tests as |
fb6b4eb
to
5d39511
Compare
This action is almost exactly the same as creating a SimpleAD so we reuse this resource and allow the user to specify the type when creating the directory (ignoring the size if the type is MicrosoftAD).
5d39511
to
82fe67f
Compare
Computed: true, | ||
Optional: true, | ||
Default: "SimpleAD", | ||
ForceNew: true, |
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.
I think we should consider adding a ValidateFunc
here in order to provide feedback as early as possible?
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.
TIL about ValidateFunc! Will do.
Hi @jszwedko! Thanks for this - it looks good to me. I've left a comment inline on the diff, so if you could let me know your opinion on that it would be great. Thanks! |
Also DRY it up a little
@jen20 added |
According to the AWS docs, creating a MS directory could take up to 25 minutes.
This adds support for creating AD Connectors. It is pretty close to the same as creating AD and simple directories so we reuse the resource.
Pushed another commit adding support for AD connectors since I was making changes in the area anyway. Let me know what you think though, I can split that one off into a separate pull request if needed, just wanted to start the conversation (and to avoid others duplicating work). |
Hi @jszwedko! This looks great! I'm going to pull it locally and run the acceptance tests but I don't see anything preventing this being merged currently. |
Actually looks like the acceptance tests are leaving dangling resources - need to investigate whether this is an issue with the changes or the original work:
|
Hi @jen20! I did see that locally, but I also saw the same error with master so I was hoping that it was just something with me. I should have some time next week to dig into it if you don't before me. |
Hey all – The |
Things look good here, pulling in, thanks! |
…service-microsoft-active-directory Add support for creating Managed Microsoft Active Directory and Directory Connectors in AWS
Awesome, thank you so much @catsby! I hadn't yet had a chance to look into this. |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This action is almost exactly the same as creating a SimpleAD so we
reuse this resource and allow the user to specify the type when creating
the directory (ignoring the size if the type is MicrosoftAD).
I also thought about overloading the
size
parameter to allow the specification ofMicrosoftAD
orEnterprise
there, but using thetype
felt closer to the actual API.