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

microsoft.logic/workflows missing "identity" property #11986

Closed
alex-frankel opened this issue Dec 7, 2020 · 16 comments
Closed

microsoft.logic/workflows missing "identity" property #11986

alex-frankel opened this issue Dec 7, 2020 · 16 comments
Assignees
Labels
Logic App Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@alex-frankel
Copy link

Originally reported here:
Azure/bicep#949

Appears to be the case for all apiVersions, but a PUT with the identity property will work as expected. Here's their template sample from docs:
https://docs.microsoft.com/en-us/azure/templates/microsoft.logic/2019-05-01/workflows

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 7, 2020
@raych1 raych1 added Logic App Service Attention Workflow: This issue is responsible by Azure service team. labels Dec 8, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 8, 2020
@ghost
Copy link

ghost commented Dec 8, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/azure-logicapps-team.

Issue Details

Originally reported here:
Azure/bicep#949

Appears to be the case for all apiVersions, but a PUT with the identity property will work as expected. Here's their template sample from docs:
https://docs.microsoft.com/en-us/azure/templates/microsoft.logic/2019-05-01/workflows

Author: alex-frankel
Assignees: raych1
Labels:

Logic App, Service Attention, needs-triage

Milestone: -

@ghost
Copy link

ghost commented Dec 22, 2020

Hi, alex-frankel. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

@ghost ghost added the no-recent-activity label Dec 22, 2020
@alex-frankel
Copy link
Author

Hi @raych1 - can you confirm that this has been successfully routed to the logic apps team? It looks like the @ mention did not work. No other participants have been added to the issue.

@ghost ghost removed the no-recent-activity label Dec 22, 2020
@alex-frankel
Copy link
Author

alex-frankel commented Dec 22, 2020 via email

@raych1
Copy link
Member

raych1 commented Dec 23, 2020

@rarayudu, @pankajsn, @tonytang-microsoft-com, I found you're either code owners of microsoft.logic RP or swagger author. Can you have a look at this issue or re-assign properly. Thanks.

@alex-frankel
Copy link
Author

alex-frankel commented Jan 11, 2021 via email

@alex-frankel
Copy link
Author

alex-frankel commented Jan 11, 2021 via email

@alex-frankel
Copy link
Author

alex-frankel commented Jan 11, 2021 via email

@miqm
Copy link

miqm commented Mar 25, 2021

@alex-frankel do you know if the team has some ETA on fixing this?

@darren-johnson
Copy link

This is an issue for me too. Is there an update on this?

@ecfan
Copy link
Member

ecfan commented Mar 30, 2021

Ping @Azure/azure-logicapps-team

@alex-frankel
Copy link
Author

Latest ETA from logic apps team is June

@Dave14393
Copy link

Is there any update on this?

@ecfan
Copy link
Member

ecfan commented Jun 3, 2021

Ping @Azure/azure-logicapps-team

@alex-frankel
Copy link
Author

Since this is taking so long to resolve, we are prioritizing Azure/bicep#3000 as a workaround. Current ETA for the swagger fix is sometime between now and end of CY2021..

The bicep workaround we are hoping to get to in our 0.5 release.

@anthony-c-martin
Copy link
Member

Closed by #16181

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Logic App Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

10 participants