Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUERY] Using Logic App SDK to provide Trigger parameter values #43654

Open
KhushaalKurswaniAnicca opened this issue Apr 25, 2024 · 3 comments
Open
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App Mgmt This issue is related to a management-plane library. needs-author-feedback More information is needed from author to address the issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@KhushaalKurswaniAnicca
Copy link

Library name and version

Azure.ResourceManager.Logic 1.0.1

Query/Question

Hi,

I have a Logic App Workflow to send email messages. The Logic App has a HTTP Request Trigger and accepts request parameters relevant to the email (to, subject, message body).

I know that I can use the HTTP trigger's URL to pass in the email parameters and trigger the workflow. However, I am looking for a way to pass parameters to the trigger using the Logic APP SDK instead of making a direct REST API call.

I previously asked a similar question (Providing parameter values when triggering Logic App Workflow). The answer to that question led me to the SDK's LogicWorkflowResource.UpdateAsync method.

The LogicWorkflowResource.UpdateAsync method can be used to update workflow parameters. Although this method works as intended, it does not meet all my requirements. Storing and modifying the email details as workflow parameters is clunky since the workflow parameters are not designed to be changed for every time the Logic App Workflow is triggered.

Instead, I am looking for a way to use the Logic App SDK to set the HTTP Trigger's request parameters. Is such a functionality supported by the Logic App SDK?

Environment

No response

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App Mgmt This issue is related to a management-plane library. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 25, 2024
Copy link

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@mcgallan mcgallan assigned mcgallan and unassigned HarveyLink May 10, 2024
@mcgallan
Copy link
Member

Hi @KhushaalKurswaniAnicca ,thank you for your feedback. I'm sorry, but the Logic App SDK currently does not support directly setting the request parameters of the HTTP trigger, so your requirement cannot be met at this time. You can see from the content of LogicWorkflowTriggerResource that the operations we can perform on the Trigger in the SDK cannot pass parameters in the call, so we cannot use the SDK to set the parameters of the Http trigger.

@mcgallan mcgallan added needs-author-feedback More information is needed from author to address the issue. and removed needs-team-attention This issue needs attention from Azure service team or SDK team labels May 14, 2024
Copy link

Hi @KhushaalKurswaniAnicca. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App Mgmt This issue is related to a management-plane library. needs-author-feedback More information is needed from author to address the issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants