v2.3.0

What's Changed

• Add net10.0 target explicitly by @wdolek in #17

Full Changelog: v2.2.0...v2.3.0

v2.2.0

What's Changed

Upgrading reference on AWSSDK.SecretsManager to [4.0.0,5.0.0) (from 3.7+).
No other functional change.

v2.1.1

What's Changed

• Rename activities to be more specific to the library by @wdolek in #14

Full Changelog: v2.1.0...v2.1.1

v2.1.0

What's Changed

• Add override accepting already loaded configuration IConfiguration by @wdolek in #13

Full Changelog: v2.0.0...v2.1.0

v2.0.0

What's Changed

• Overall refactoring/API changes, see below
• Reintroduce observability by @wdolek in #8
• Introduce source builder by @wdolek in #11
• Instead of creating logger once, create it before every fetch (allow hacking in different logger factory instance) by @wdolek in #12

Full Changelog: v1.2.0...v2.0.0

Breaking changes

• Errors have to be handled explicitly using OnLoadException and OnReloadException
  • ⚠️ When using polling watcher, exceptions are NOT swallowed by default
• When passing AWS Secrets Manager client (IAmazonSecretsManager), client is first and secret name second
• SecretsManagerConfigurationProviderOptions removed, instead, SecretsManagerConfigurationSource is configured directly
  • Implies removal of configuration override accepting configure action of SecretsManagerConfigurationProviderOptions

v1.2.0

Is there anything new?

• dropped support of net6.0
• targeting only: net8.0 and net9.0
• fix: not wrapping SecretRetrievalException in itself when SecretFetcher fails to fetch the secret

v1.1.0

What's Changed

• Add multiple secrets as source at once by @wdolek in #1
• ⚠️ Breaking change: Remove extension methods with default isOptional parameter by @wdolek in #2
• ⚠️ Breaking change: Require AWSSDK.SecretsManager v3.7.0 or later by @wdolek in #3

Full Changelog: v1.0.0...v1.1.0

Change detail

Fetch multiple secrets:

builder.Configuration.AddSecretsManager(["my-first-secret", "my-second-secret"]);

Instead isOptional parameter, configure options:

// removed, API no longer available
builder.Configuration.AddSecretsManager("my-secret-secrets", isOptional: true);

// replaced by use of configure callback
builder.Configuration.AddSecretsManager("my-secret-secrets", c => c.IsOptional = true);

---

Breaking change in minor version: package is not widely used - limited impact; loading secret as optional seems to be very niche usecase

v1.0.0

Version 1.0.0

🥳 First stable:

• finalized API (see README)
• fixed tiny issue when tokenizer added leading delimiter ":" to configuration key without prefix
• improved test coverage 🤷

Full Changelog: v0.2.0-alpha...v1.0.0

v0.2.0-alpha

What's new

• possibility to use IConfigurationWatcher for triggering configuration value refresh
  • including SecretsManagerPollingWatcher for simple polling (based on given interval)
• startup timeout configuration: if provider fails to load secret in given time, exception is thrown
• provider optionality: it is possible to set configuration source as optional, meaning exception is not thrown on failure
• logging of provider events (requires ILoggerFactory instance)

Full Changelog: v0.1.0-alpha...v0.2.0-alpha

v0.1.0-alpha

🥳 Initial implementation of AWS SecretsManager configuration provider

There are still rough edges and API is not finalized yet, though basic functionality is there and working as expected.

Full Changelog: https://github.com/wdolek/w4k-extensions-configuration-aws-secretsmanager/commits/v0.1.0-alpha