Steeltoe
Steeltoe copied to clipboard
Add support for Application Configuration Service
Description
Adds a post-processor that remaps all non-system keys (eg: type and provider) to the root of the IConfiguration
Fixes #1195
Quality checklist
- [ ] Your code complies with our Coding Style.
- [ ] You've updated unit and/or integration tests for your change, where applicable.
- [ ] You've updated documentation for your change, where applicable. If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
- [ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
- [ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.
This should be ready after we make sure hierarchy is support in config keys via double-underscore, the same as documented in Microsoft's key-per-file provider
This work is being deprioritized right now, if it would mean something to you (the reader of this message) please let us know and we'll finish it up and ship it
This PR has test failures in Connectors, which doesn't show up in the checks because Steeltoe.All has not run. This proves having only component builds is fundamentally unreliable, as the trigger conditions are unaware of project dependencies. So I propose we always run the full build on PRs, not as a manual step.
/azp run Steeltoe.All
Azure Pipelines successfully started running 1 pipeline(s).
This PR has test failures in Connectors, which doesn't show up in the checks because Steeltoe.All has not run. This proves having only component builds is fundamentally unreliable, as the trigger conditions are unaware of project dependencies. So I propose we always run the full build on PRs, not as a manual step.
Or we could add the dependencies to the component builds... but Steeltoe.All does run a lot faster than it did a year or two ago, so I'm open to trying out that change
Or we could add the dependencies to the component builds... but Steeltoe.All does run a lot faster than it did a year or two ago, so I'm open to trying out that change
That'll break sooner than later. I prefer to add Steeltoe.All, so we'll have some quick feedback from the component builds, while at the same time validating the full build.
Azure Pipelines successfully started running 1 pipeline(s).
/azp run Steeltoe.All
Azure Pipelines successfully started running 1 pipeline(s).
Quality Gate passed
Issues
4 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code