mirror of
https://github.com/larksuite/cli.git
synced 2026-07-07 00:55:53 +08:00
4422265d5f
`im chats link` is registered as a regular service method (no `risk: high-risk-write` annotation), so the framework does not register the `--yes` flag on it. Setting `Yes: true` on the e2e Request makes the runner append `--yes`, which cobra rejects with `unknown flag: --yes` before the request is ever issued — the rest of the assertions then fall through with empty stdout. The flag was added in #633 alongside the risk-tiering rollout that covered other workflows that genuinely flipped to high-risk-write. For chats link the API call (creating a chat share link with a configurable validity period) is not destructive and was never re-classified, so the line is just leftover from that pass. Drop it to restore the e2e green; if we ever decide to gate share-link creation behind confirmation we can re-add it together with the metadata flip. Change-Id: Ieb094407a7f0fa18cd130a9d80c7146274b5ecc7