CLI fails to parse empty dates from API responses

TL;DR

What was reported: Issue fastly/cli#1880 (closed, 8 comments): ...

2. What works:

[rcaril (maintainer)]: The customsignal create and list CLI errors mean your Fastly Control Panel account is not linked to your NGWAF Corp. Follow the Fastly guide Connecting a Fastly Account to Your Corp to grant API access. Meanwhile, you can hit /ngwaf/v1/workspaces/{id}/signals directly with curl instead of the CLI.

When to use

You are seeing this: Bug reports opened here: - Do not have an SLA - Should not be a duplicate of an existing support ticket that you have already created, or vice versa - May take longer to solve compared to our dedicated support team More details on submitting issues can be... Use this skill when you run into "CLI fails to parse empty dates from API responses".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://support.fastly.com
• https://github.com/fastly/cli/blob/main/ISSUES.md

In the GitHub issue, the reporter asked: CLI fails to parse empty dates from API responses. The working answer that came out of the thread: [rcaril (maintainer)]: The customsignal create and list CLI errors mean your Fastly Control Panel account is not linked to your NGWAF Corp. Follow the Fastly guide Connecting a Fastly Account to Your Corp to grant API access. Meanwhile, you can hit /ngwaf/v1/workspaces/{id}/signals directly with curl instead of the CLI. Source: https://github.com/fastly/cli/issues/1880