Adding support for Active Directory organizational units (OU) #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Complex active directories organise resources like computers and users into sub-partitions, called Organizational Units (OU). This is a common requirement for all, but the smallest, Active Directories.
While the CVS API offers the functionality to set the OU, the current CVS/GCP UI misses that functionality. This PR enables OU handling for the Terraform provider.
Note to maintainers: I also added checks into active directory acceptance tests. I cannot test this, but should work fine without issues. Please note, that you have to add an OU called "engineering" to your test AD, if you want to create volumes after you set OU=engineering. Otherwise SMB volume create will fail, because the OU doesn't exist.