spring-cloud-aws
spring-cloud-aws copied to clipboard
AppConfig integration
:loudspeaker: Type of change
- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
:scroll: Description
Still have to go through it once more time and add some docs. Tried against real AWS and all tests are passing. Since AWS Localstack has a bug it is not possible to make a real integration test. Closes #465
@eddumelendez SInce you worked on AppConfig integration before please when you have time check the design. I will do more cleaning and polishing of the code.
:bulb: Motivation and Context
:green_heart: How did you test it?
:pencil: Checklist
- [x] I reviewed submitted code
- [x] I added tests to verify changes
- [x] I updated reference documentation to reflect the change
- [x] All tests passing
- [x] No breaking changes
:crystal_ball: Next steps
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
3 Code Smells
No Coverage information
0.0% Duplication
What is holding this back? I'm waiting eagerly for this feature since months.
Hey @noshua , it is planned go be tackled once 3.0.0 is released. There are some minor work to be done on this PR.
It would be cool to include tests with localstack once is implemented -> https://github.com/localstack/localstack/issues/6891
I'm also eagerly waiting for the feature. How can I help to get it integrated?
any updates?
This feature would be awesome! Keeping an eye on this, and willing to help if needed.
I feel like I must have missed it but can you clarify what happens when a new AppConfig HostedVersion
gets pushed to the application and environment? Does it force a reload of the context?
@MatejNedic Localstack implemented Appconfig support
@maciejwalkowiak didn't know that perfect. Will implement with LocalStack tests and we can then hopefully merge and release. One more thing is that we will need to put LocalStack PRO credentials in GitHub pipeline
Hey @NChitty , if you enable reload inside of integration it will periodically call AppConfig and do a reload or refresh depending on what you choose. It is covered by documentation.
I don't wanna be rude, but over a year has passed by since my last status request. Is this feature dead before arrival?!
Hey @noshua , I am thinking about redoing this integration. I have to rethink it, don't like current implementation can do more things will be exploring it.