Remove verbose mode in CLI tool, always surface all errors
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3560941. -->
Reported by: [balintbrews](https://www.drupal.org/user/613760)
Related to !394
>>>
<h3>Overview</h3>
<p>The CLI tool currently supports a <code>--verbose</code> flag and a <code>CANVAS_VERBOSE</code> environment variable in its config files. Full error details are only displayed when these are enabled — for instance, when HTTP errors are returned by the Drupal backend.</p>
<p>This approach is problematic because error details are usually essential for diagnosing issues. For example, HTTP 422 errors occur when there's a problem with a <code>component.yml</code> metadata file. Without verbose mode enabled, users have no way to identify the specific issue.</p>
<h3>Proposed resolution</h3>
<ol>
<li>Audit the codebase for the use of verbose mode, and ensure all errors are always displayed. Make sure they're shown within the summary tables when they can be connected to an operation with a specific component.</li>
<li>Parse and make the output of HTTP responses more friendly.</li>
</ol>
<p><strong>Example error response:</strong> — see the error schema in <code>openapi.yml</code>, or look into the actual code</p>
<pre><pre>{<br> "errors": [<br> {<br> "detail": "[id] Does not match the regex pattern ^[a-z]([a-zA-Z0-9_-]*[a-zA-Z0-9])*:[a-z]([a-zA-Z0-9_-]*[a-zA-Z0-9])*$\n[machineName] Does not match the regex pattern ^[a-z]([a-zA-Z0-9_-]*[a-zA-Z0-9])*$",<br> "source": {<br> "pointer": ""<br> }<br> },<br> {<br> "detail": "The <em class="placeholder">&quot;Card&quot;</em> machine name is not valid.",<br> "source": {<br> "pointer": "machineName"<br> }<br> }<br> ]<br>}</pre></pre><h3>User interface changes</h3>
<p>CLI output always shows all error details.</p>
issue