-
Notifications
You must be signed in to change notification settings - Fork 103
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
[BUG] Functions no longer callable from logic apps after migrating to V2 model (python) #1439
Labels
Comments
ManelBH
changed the title
[BUG] Functions no longer available to logic apps after migrating to V2 model (python)
[BUG] Functions no longer callable from logic apps after migrating to V2 model (python)
Mar 5, 2024
Thanks for reporting will check and update. |
Hi @ManelBH are you trying like this.seems working fine.if not please mention all the steps.Thanks |
bhagyshricompany
added
needs-author feedback
and removed
Needs: Triage (Functions)
labels
Mar 15, 2024
Hi @bhagyshricompany, I'm using Consumption Logic Apps. |
microsoft-github-policy-service
bot
added
needs-attention 👋
and removed
needs-author feedback
labels
Mar 15, 2024
ok will update. |
@gavin-aguiar pls comment and validate.Thanks |
Any news? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Investigative information
Repro steps
1 - Define a function using the V2 python model and blueprints:
Expected behavior
I can select the "http_trigger" method just like with the V1 model.
Actual behavior
The list of available methods is empty
Contents of the requirements.txt file:
Notes:
The same behaviour is observed when using blueprints:
The text was updated successfully, but these errors were encountered: