Skip to content

Releases: Kralizek/AWSSecretsManagerConfigurationExtensions

v1.7.0

08 Nov 14:44
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.6.3...v1.7.0

Version 1.6.3

08 Sep 09:19
Compare
Choose a tag to compare
  • Added XML comments to properties of SecretsManagerConfigurationProviderOptions #60

Thanks @devklick for the contribution!

Version 1.6.2

19 May 12:58
7a2dd15
Compare
Choose a tag to compare
  • Fill the name of the SecretListEntry from the GetSecretValueResponse when options.AcceptedSecretArns is specified #54

Thanks to @ycherkes for fixing this issue.

Version 1.6.1

29 Apr 08:56
9257021
Compare
Choose a tag to compare

Fixed small issues created in version 1.6.0

  • An excessive amount of exceptions was thrown while testing if a secret value is a json snippet #52
  • Missing Name property when AcceptedSecretArns configuration is populated #51

Special thanks to @ycherkes (aka @smurtdev) for his help.

Version 1.6.0

27 Apr 09:04
295571d
Compare
Choose a tag to compare
  • Added possibility to specify a list of ARNs to access rather than scanning all available secrets #46
  • Added possibility to use AWS SecretsManager filters capabilities #47
  • Made JSON detection more robust #50

Thanks @scott-phillips-ah, @ycherkes, @smurtdev, @mirkogeffken

Version 1.5.0

22 Jan 08:59
277a7f2
Compare
Choose a tag to compare

Added possibility to explicitly force the reload of the configuration (#42)

Thanks @TheRubble

Version 1.4.1

21 Jul 17:32
016ad24
Compare
Choose a tag to compare
  • Aligned the provider with .NET recommendations about case-sensitiveness of underlying dictionary (#32)

Thanks @Erwinvandervalk

Version 1.4.0

16 Jul 12:42
122a869
Compare
Choose a tag to compare
  • Add support for custom client factory (#30)

Version 1.3.0

14 Jul 09:42
56d34a4
Compare
Choose a tag to compare
  • Added support to refresh the provider with updated secrets via polling (#23)

Thanks @manuel-guilbault

Version 1.2.1

08 Feb 18:14
0affd9d
Compare
Choose a tag to compare
  • Fixed an issue with secrets whose plain text value contained a JSON string representing an array of complex objects. #22

Thanks @udlose