feat: add cloud flow authoring skill and connector discovery - #177
Open
zekelinAlex wants to merge 1 commit into
Open
feat: add cloud flow authoring skill and connector discovery#177zekelinAlex wants to merge 1 commit into
zekelinAlex wants to merge 1 commit into
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.
Adds a
connectornoun group undertxc environmentfor discovering what the connected environment offers to cloud flows:listshows the connectors available in the environment,operation listshows a connector's operations classified as action/trigger/webhook-trigger, andoperation getprints one operation's exact parameter names, types, enums and dynamic markers distilled from the connector's swagger. Body parameters come out slash-joined (emailMessage/To), which is the key format flow definitions use in inputs.parameters, so nothing has to be guessed when authoring a flow.The API is api.powerapps.com with the same service.powerapps.com token audience the BAP admin client already acquires, so auth needed no new code; environment id comes from the connection with a catalog lookup fallback. The swagger distiller resolves $ref/allOf, caps nesting depth, filters internal/readOnly fields and marks dynamic-schema bodies as dynamic.
There's also a new flow-development docs skill covering the local-first flow authoring chain (pp-flow triggers, definition JSON rules, connection references), wired into component-creation, the composition chains and the skills index.