Saptune status projection #1821
Merged
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
arbulu89
requested review from
EMaksy,
dottorblaster,
rtorrero and
CDimonaco
and removed request for
dottorblaster
arbulu89
force-pushed
the
saptune-status-projection
branch
from
5de7ae0 to
6b0f636
Compare
CDimonaco
approved these changes
Sep 14, 2023
EMaksy
approved these changes
Sep 14, 2023
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
Saptune status projection.
The read model and the view follows a flat hierarchy adding
saptune_statusdirectly. In the future we could have other entries likesaptune_notesorsaptune_solutions.We could have other "tree" kind of representations as well. Check the open api schema to see how it looks like
How was this tested?
Tested with UT