Skip to content

Conversation

@WhitWaldo
Copy link
Contributor

Description

Just added a simple unit test to the Secrets API test suite to validate that a secret that contains forward slashes in it would have the secret name properly realized through and through (e.g. that it wouldn't limit to any single part of the path).

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: Not a filed issue so much as a concern raised on Discord.

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • [N/A] Extended the documentation

@WhitWaldo WhitWaldo requested review from a team as code owners September 13, 2024 05:41
@WhitWaldo WhitWaldo self-assigned this Oct 3, 2024
@WhitWaldo
Copy link
Contributor Author

@philliphoff or @halspang When you have a moment, would you please give this a quick once-over so we can merge it?

No impact on the client - just adding a unit test to validate coverage for a concern raised on Discord.

@WhitWaldo WhitWaldo added this to the v1.15 milestone Oct 7, 2024
@WhitWaldo WhitWaldo merged commit 4d78706 into dapr:master Oct 11, 2024
10 checks passed
@WhitWaldo WhitWaldo deleted the additional-secrets-testing branch October 11, 2024 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants