check for case sensitivity at delete for user and group paths, modify… #29922
Conversation
This file contains hidden or 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
… tests to cover proper deletions
|
CI Results: |
|
Build Results: |
VioletHynes
approved these changes
Mar 14, 2025
fairclothjm
approved these changes
Mar 14, 2025
|
Hi @stevendpclark! I just wanted to confirm, do we need to remove the tag for backport/1.18.x because the branch is blocked? Wanted to double check if we need to add it later? |
|
@aslamovamir You should use the enterprise 1.18.x tag as you have, we won't be doing any more 1.18 CE releases now that 1.19 is out so effectively that branch is no longer maintained. |
Ah okay, thanks for clarifying! |
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.
Description
What does this PR do?
Fixes a bug that does not properly delete users and groups by first converting their names to lowercase when case senstivity option is off. This bug was raised from community here: #29355
Added unit tests and manually tested by rerunning the commands that was run to reproduce the bug (check here for more details):
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.