I was attempting to retrieve information about licensing plans that can be associated with a flow, and I realized that while the flow get command returns a lot of terrific and useful information, it appears to be missing some properties that Microsoft now returns by default using an $expand query parameter when fetching flow details.
Currently, the CLI fetches flow data with the following URL:
/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}?api-version=2016-11-01
While visiting the Front End flow details page, the fetch is more like:
/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}?$expand=swagger,properties.connectionreferences.apidefinition,properties.definitionsummary.operations.apioperation,operationDefinition,plan,properties.throttleData,properties.estimatedsuspensiondata,properties.licenseData&api-version=2016-11-01
I guess firstly I would like to confirm that this appears to be standard to others as well, and not just something unique to my environments. 😅
If it is the new standard, then I think it would be useful to include these additional properties in the JSON response for flow get.
I don't think we would need to over-complicate it by including an additional "option" that a user must include, but rather just code this part into the request by default.
I was attempting to retrieve information about licensing plans that can be associated with a flow, and I realized that while the
flow getcommand returns a lot of terrific and useful information, it appears to be missing some properties that Microsoft now returns by default using an$expandquery parameter when fetching flow details.Currently, the CLI fetches flow data with the following URL:
/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}?api-version=2016-11-01While visiting the Front End flow details page, the fetch is more like:
/providers/Microsoft.ProcessSimple/environments/{environmentName}/flows/{flowName}?$expand=swagger,properties.connectionreferences.apidefinition,properties.definitionsummary.operations.apioperation,operationDefinition,plan,properties.throttleData,properties.estimatedsuspensiondata,properties.licenseData&api-version=2016-11-01I guess firstly I would like to confirm that this appears to be standard to others as well, and not just something unique to my environments. 😅
If it is the new standard, then I think it would be useful to include these additional properties in the JSON response for
flow get.I don't think we would need to over-complicate it by including an additional "option" that a user must include, but rather just code this part into the request by default.