feat: add flow-runs reader to env log (#41) - #182
Open
zekelinAlex wants to merge 3 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #141: this branch is cut from users/alexander.zekelin/env-log-reader and adds to the same env log group, so the diff includes its commits until it merges.
Adds a flow-runs reader to the env log group: txc env log flow-runs --flow lists recent runs of one cloud flow (status, trigger type, start/end, duration, error), --run-id shows a single run, --status and --top filter the list. The flow is resolved from the workflow table (category 5) by name or guid, with friendly errors for unknown and ambiguous names.
Runs are read from the flowrun virtual table instead of the flow API on purpose: the flow service rejects tokens for pac's first-party client id with AADSTS65002 (preauthorization required), so per-action details aren't reachable from this CLI at all. The flowrun table proxies the same run history under the ordinary Dataverse token and covers the run level; the limitation is documented on the contract.