[logic] There is unexpected line break in outputs of az logic workflow show command with --output yaml option

[azclibot]

Source: Azure/azure-cli#31982 (by ShingoHanai)
Affected extension: logic (src/logic/)

---

<<UNTRUSTED:issue-31982>>

Issue #31982 (by ShingoHanai)

Title

There is unexpected line break in outputs of az logic workflow show command with --output yaml option

Body

Describe the bug

In case of workflow contains compose action input expression "@greaterOrEquals(ticks(addSeconds(utcNow(), 5)) ,ticks(convertToUtc('2050-06-01T00:00:00', 'Tokyo Standard Time')))", result is like below.

• command
  az logic workflow show --resource-group logicapps --name array --output yaml

• part of unexpected line break
  ''' definition: $schema: https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json# actions: Compose: inputs: '@greaterOrEquals(ticks(addSeconds(utcNow(), 5)) ,ticks(convertToUtc(''2050-06-01T00:00:00'', ''Tokyo Standard Time'')))' runAfter: {} type: Compose '''

My customer requires this unsxpected line break removal.
Can we fix it or is it by design?

Related command

az logic workflow show --resource-group logicapps --name array --output yaml

Errors

No error happed, but result contains unexpected line break.

Issue script & Debug output

PS C:\Users\shhanai> az logic workflow show --resource-group logicapps --name array --output yaml
accessControl: {}
accessEndpoint: https://prod-08.japaneast.logic.azure.com:443/workflows/6f5374ff8da24c5d8c60703cac296f43
changedTime: '2025-07-29T06:43:17.3771708Z'
createdTime: '2024-07-02T01:28:28.7045754Z'
definition:
$schema: https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#
actions:
Compose:
inputs: '@greaterOrEquals(ticks(addSeconds(utcNow(), 5)) ,ticks(convertToUtc(''2050-06-01T00:00:00'',
''Tokyo Standard Time'')))'
runAfter: {}
type: Compose
contentVersion: 1.0.0.0
outputs: {}
parameters:
$connections:
defaultValue: {}
type: Object
triggers:
Recurrence:
evaluatedRecurrence:
frequency: Month
interval: 3
recurrence:
frequency: Month
interval: 3
type: Recurrence
endpointsConfiguration:
connector:
outgoingIpAddresses:
- address: 13.73.21.230
- address: 13.71.153.19
- address: 13.78.108.0/28
- address: 40.79.189.64/27
- address: 20.89.11.48/28
- address: 20.89.11.64/27
- address: 20.89.163.17
- address: 20.89.163.9
workflow:
accessEndpointIpAddresses:
- address: 13.71.146.140
- address: 13.78.84.187
- address: 13.78.62.130
- address: 13.78.43.164
- address: 20.191.174.52
- address: 20.194.207.50
- address: 20.18.198.232
- address: 20.18.197.179
- address: 20.18.198.148
- address: 20.18.238.86
- address: 4.189.8.207
- address: 4.189.9.80
- address: 4.189.10.88
- address: 4.189.8.209
- address: 172.207.65.96
- address: 172.207.65.97
outgoingIpAddresses:
- address: 13.71.158.3
- address: 13.73.4.207
- address: 13.71.158.120
- address: 13.78.18.168
- address: 13.78.35.229
- address: 13.78.42.223
- address: 13.78.21.155
- address: 13.78.20.232
- address: 20.191.172.255
- address: 20.46.187.174
- address: 20.194.206.98
- address: 20.194.205.189
- address: 20.18.198.224
- address: 20.18.197.177
- address: 20.18.198.141
- address: 20.18.238.83
- address: 4.189.14.67
- address: 4.189.8.211
- address: 4.189.9.135
- address: 4.189.8.208
- address: 20.210.69.32
- address: 20.210.69.33
id: /subscriptions/f50fbafe-e4aa-4976-8168-1a136a15849e/resourceGroups/logicapps/providers/Microsoft.Logic/workflows/array
identity:
principalId: 528d56c8-9e22-43b5-b53e-6822cf3eda3e
tenantId: 16b3c013-d300-468d-ac64-7eda0820b6d3
type: SystemAssigned
location: japaneast
name: array
parameters:
$connections:
value: {}
provisioningState: Succeeded
resourceGroup: logicapps
state: Enabled
tags: {}
type: Microsoft.Logic/workflows
version: 08584478354881066617

Expected behavior

Outputs doesn't include unexpected line break.

Environment Summary

PS C:\Users\shhanai> az version
{
"azure-cli": "2.76.0",
"azure-cli-core": "2.76.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"graphservices": "1.0.0b1",
"logic": "1.1.0"
}
}

Additional context

No response

Comments

Comment by Yong Zhang (@yonzhan)

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

Comment by ShingoHanai

Yong Zhang (@yonzhan) Do you have any update?

Comment by Nobuko YAMADA (@nobuko-yamada)

Yong Zhang (@yonzhan) Thank you for checking this. It would be very helpful if you could provide any updates or insights regarding a possible workaround.
<<END:issue-31982>>

[yonzhan]

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

[azclibot]

Hi Copilot! Please fix the following bug in the logic Azure CLI extension.

Issue Summary

Command: az logic workflow show --resource-group <rg> --name <name> --output yaml

Bug: When the workflow definition contains long string expressions (e.g., @greaterOrEquals(ticks(addSeconds(utcNow(), 5)), ticks(convertToUtc('2050-06-01T00:00:00', 'Tokyo Standard Time')))), the YAML output formatter wraps these strings at ~80 characters, inserting unexpected line breaks.

Expected behavior: Long string values should not be wrapped with line breaks in YAML output. The YAML output should preserve string values on a single line.

Root cause area: The YAML formatter in the extension or azure-cli-core uses PyYAML's default width setting which wraps long strings. The fix is to set width=float('inf') (or a very large value) in the YAML dumper configuration so that long strings are not line-wrapped.

Look at how the YAML output formatter works in the extension or in azure-cli-core's output module (azure/cli/core/output.py or similar), and update the YAML dump call to avoid wrapping long strings.

Environment

• CLI version: 2.76.0
• Extension: logic 1.1.0
• OS: Windows (PowerShell)

Reference

Tracked from Azure/azure-cli#31982.

---

PR title & description format (required)

This repo enforces a PR format (guide). Please author the PR exactly as follows or CI's Check the Format of Pull Request Title and Content will fail.

Title

• Start with [Logic] — square brackets [] for a customer-facing change (added to HISTORY.rst), curly {} if not. A bug fix is customer-facing, so use [].
• Then Fix #10032: to link the issue (use the short #N form, not owner/repo#N).
• Then the affected command wrapped in backticks followed by a colon — e.g. `az vm create`:. ⚠️ The format check fails if the az ... command in the title is not inside backticks.
• Then a present-tense, capitalized verb (Fix for bug fixes; Add/Change/Deprecate/Remove otherwise) and a concise summary.
• Recommended title (note the backticks around the command):

[Logic] Fix #10032: `az <command>`: Fix <concise description of the fix>

Description — follow the PR template and fill in:

• Link the issue — start the Description with a closing keyword so the PR auto-links and closes it: Fixes #10032.
• Related command — the az ... command this affects.
• Description (mandatory) — why the bug happens, what you changed, and the resulting behavior.
• Testing Guide — example command(s) showing the fix works.
• History Notes — leave the title to drive the history note, or add extra lines in the same format (component in brackets + the command in backticks), e.g. [Logic] `az <command>`: <note>.
• Keep the template checklist and tick the items you've satisfied.

---

Posted by agent-assist (autonomous bug-fix pipeline).