feat: add odigos describe analyze phase to make the info accessible to tools #1633
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
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.
Until this PR, everytime we calculated the
odigos describeoutput, we transformed it to text, which makes it less useful to be used in odigos ui and other tools, as the data is human readable and not machine readable.This PR separates the 2 tasks. Now one can simply get the results of the
odigos describecommand and now immediately if something is still in transit or has errors.Tools can process this data to display it nicely or act upon it. This function offers an handy aggregation for the relevant data in the context of odigos entities.