feat (zero downtime deploy) - event receivers programmatic stop/start #164
Conversation
This file contains 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
pietro-tota
changed the title
* feat(zero-downtime-deploy): openapi for receiver stop/start * feat(zero-downtime-deploy): openapi * fix: spotless apply * fix: update doc refs * fix: openapi generation execution id * feat(zero-downtime-deploy): redis integration (#157) * feat(zero-downtime-deploy): redis integration * feat(zero-downtime-deploy): openapi for receiver stop/start * feat(zero-downtime-deploy): openapi * feat: add redis template wrapper implementation * feat: add redis template wrapper implementation * feat: add redis template wrapper implementation * feat(zero-downtime-deploy): add control bus integration (#158) * feat: add control bus integration * feat: add junit tests * feat(zero downtime deploy): add redis stream consumer (#160) * feat(zero downtime deploy): add redis stream consumer * feat(zero downtime deploy): receiver status service + status poller (#161) * feat(zero downtime deploy): receiver status service + status poller * feat(zero downtime deploy): event receivers api commands (#163) * feat(zero downtime deploy): event receivers api comnmand * chore(typo): change redis template parameters * fix: deployment pipeline (#165) * fix: enable scaled object for all envs
|
🎉 All dependencies have been resolved ! |
|
This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size. |
|
scaminati-bv
approved these changes
Jan 24, 2025
CianoDanilo
approved these changes
Jan 24, 2025
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.
Depends on #156
List of Changes
This PR will be a container for all decomposed zero downtime deploy event receivers programmatic stop/start.
The following PRs will be merged into this one to perform a single release/merge to main branch:
Motivation and Context
This PR once merged, will contain the merged development for the zero downtime deployment.
The zero downtime deployment is mandatory in order to guarantee that no event is lost during deployment phase while always leaving a event receiver instance up and running while swapping from staging to prod deployments
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
expected)
Checklist: