-
Notifications
You must be signed in to change notification settings - Fork 141
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
ADManagedServiceAccount: Add CommonName parameter #661
ADManagedServiceAccount: Add CommonName parameter #661
Conversation
Codecov Report
@@ Coverage Diff @@
## main #661 +/- ##
===================================
Coverage 98% 98%
===================================
Files 25 25
Lines 3408 3420 +12
===================================
+ Hits 3340 3352 +12
Misses 68 68
|
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.
Reviewable status: 0 of 4 files reviewed, 1 unresolved discussion (waiting on @Antiohne)
a discussion (no related file):
This PR needs integration tests.
Have you tested this change through the full lifecycle of an ADManagedServiceAccount object and this additional property? i.e. addition, modification and deletion of an ADManagedServiceAccount with and without this property, and addition, modification and deletion of this property. This must be a non-breaking change to current usage of this resource.
Labeling this pull request (PR) as abandoned since it has gone 14 days or more since the last update. An abandoned PR can be continued by another contributor. The abandoned label will be removed if work on this PR is taken up again. |
Yes this change is non-breaking and is based on the ADUser implementation. If you do not specify a common name the common name of the Managed User Identity will be the same as the SamAccountName. When specified the common name will be different to the SamAccountName and the Distinguished Name will be based on the specified common name. The existing integration tests will now test that the value of the common name is the same as the SamAccountName. Additional tests are added for the creation and deletion of a managed service account with a common name. Another test will check the rename of that common name. |
Labeling this pull request (PR) as abandoned since it has gone 14 days or more since the last update. An abandoned PR can be continued by another contributor. The abandoned label will be removed if work on this PR is taken up again. |
@X-Guardian : This change is ready for reviewing. The required integration tests are added and the full lifecycle is tested. |
@X-Guardian : The requested integration tests are added in September. Is this PR now ready for review? |
Labeling this pull request (PR) as abandoned since it has gone 14 days or more since the last update. An abandoned PR can be continued by another contributor. The abandoned label will be removed if work on this PR is taken up again. |
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.
Reviewed 3 of 4 files at r1, 2 of 3 files at r2, 1 of 1 files at r4.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @X-Guardian)
I push this through so we can iterate from here. |
Pull Request (PR) description
Added support for setting a common name to a Managed Service Account for a longer more friendly name than the SAM account name which has a 15 character limit.
This Pull Request (PR) fixes the following issues
Task list
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
and comment-based help.
This change is