NAS-109732 / 12.0 / Clear various AD-related caches when service explicitly stopped #6573
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.
A not-insignificant number of users will first try deploying TrueNAS
in a lab / test domain before migrating to the final production domain.
This may be done haphazardly without cleanly leaving the old AD domain.
To ease the migration process, we should clear out middleware user
cache when the AD service is explicitly stopped and flush samba caches.