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

az logic workflow create/update removes existing parameters #7537

Open
NathZ1 opened this issue Apr 21, 2024 · 2 comments
Open

az logic workflow create/update removes existing parameters #7537

NathZ1 opened this issue Apr 21, 2024 · 2 comments
Assignees
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@NathZ1
Copy link

NathZ1 commented Apr 21, 2024

Describe the bug

I am using terraform (azurerm provider) to create Azure Logic App resources. These have configured parameters for API connections that are used within the Logic Apps. I then have a separate repo where the definitions are kept, and use Azure CLI to update them as part of my deployment pipeline.

What I am finding is that whenever I update the Logic Apps via the Azure CLI (az logic workflow create/update), it updates the definition as expected, however it replaces the template object with {}. As the template object state is initially created and managed by terraform, I need this to be retained after the update.

I thought I could just remove the parameters object from JSON definition that is used, but that didn't work... -

{
  "definition": {
    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
    "actions": {...},
    "contentVersion": "1.0.0.0",
    "outputs": {},
    "parameters": {
      "$connections": {
        "defaultValue": {},
        "type": "Object"
      }
    },
    "triggers": {...}
    }
  }, 
////removed the "parameters" object from here
}

This may be my lack of understanding, but is there a way to retain this when passing updated definition to retain the parameters?

Related command

az logic workflow create/update

Errors

No error, but not expected functionality

Issue script & Debug output

.

Expected behavior

parameters is retained after update of definitions

Environment Summary

azure-cli: 2.56
azure-extensions: 1.1.0

Additional context

No response

@NathZ1 NathZ1 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 21, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Apr 21, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App Auto-Assign Auto assign by bot labels Apr 21, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 21, 2024
@yonzhan yonzhan added this to the Backlog milestone Apr 21, 2024
@yonzhan yonzhan added the Azure CLI Team The command of the issue is owned by Azure CLI team label Apr 21, 2024
@NathZ1
Copy link
Author

NathZ1 commented Jul 2, 2024

any update on this @yonzhan? In addition to the above, I have also noticed that existing resource Tags are removed as well which is an added annoyance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team customer-reported Issues that are reported by GitHub users external to the Azure organization. Logic App 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

5 participants