v2.0.0 multiple S3 backends and Session Tags
What's Changed
Support the nested claims format for webidentity tokens as how AWS supports it. This allows to set session tags when assuming a role with a webidentity token. This allows to influence policies based out of attributes in your identity store (See unit test if it is unclear what type of policy is meant)
- !Feature/proxy multiple backends issue3 by @pvbouwel in #7 & #9
Since we are a proxy we don't need a 1-to-1 relationship with a single S3 proxy. We allow specifying now multiple S3 backends and selection of which backend is done based out of the region attribute of the request. This means that at time of writing we are still limited to a single backend per region which seems not too limiting (If this is would be an issue to you open an issue and explain your use case for multiple backends within a region).
BREAKING CHANGE: This change expects that a valid region is passed in otherwise it fails. If this is unwanted you could still specify a default region and enable config flag "ENABLE_LEGACY_BEHAVIOR_INVALID_REGION_TO_DEFAULT_REGION" but this should only be used for transition periods with a grace period since allowing invalid region names is something that becomes harder to migrate away from over time (as invalid client configurations keep on increasing)
BREAKING CHANGE: The configuration format is overhauled to support defining multiple backends and the original environment variables have been removed. See README.md on how to configure it following the new format.
Full Changelog: v1.0.0...v2.0.0
