feat: add support for config aggregator #214
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ocofaigh
requested review from
MatthewLemmond and
Aayush-Abhyarthi
as code owners
|
/run pipeline |
ocofaigh
requested review from
jor2
and removed request for
MatthewLemmond and
Aayush-Abhyarthi
|
/run pipeline |
|
As expected upgrade test failed since the directory of example was renamed. Low risk since not changing any current module code (just adding new code to enable config aggregator and create a trusted profile), so skipping |
|
/run pipeline |
|
/run pipeline |
|
Going to add enterprise support to this PR |
…-app-configuration into aggre
|
/run pipeline |
MatthewLemmond
requested changes
May 2, 2025
|
/run pipeline |
MatthewLemmond
approved these changes
May 2, 2025
|
🎉 This PR is included in version 1.4.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
See #213
NOTE: Enterprise support will be coming in a subsequent PR
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers