Immutable solution version
The `viceroy_version` field seems to not be working
Complete solution
Shows how to fix the `viceroy_version` field seems to not be working. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
[Integralist (maintainer)]: Fixed in the Fastly CLI (PR #1039): compute serve was neglecting to install Viceroy's environment files alongside the dependency, which broke the viceroy_version field. Update the Fastly CLI to a release containing that fix and it works again.
Steps
- [Integralist (maintainer)]: Fixed in the Fastly CLI (PR #1039): compute serve was neglecting to install Viceroy's environment files alongside the dependency, which broke the viceroy_version field.
- Update the Fastly CLI to a release containing that fix and it works again.
When to use
You are seeing this: https://github.com/fastly/cli/issues/1037: Issue fastly/cli#1037 (closed, 8 comments): Version Fastly CLI version v10.4.0 (4b869ab3) Built with go version go1.21.0 linux/amd64 Viceroy version: viceroy 0.9.1 What happened This morning, we noticed a new... Use this skill when you run into "The viceroy_version field seems to not be working".
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
Versions mentioned in the source: v10.4.0, viceroy 0.9.1, 0.9.0. If you are on something much newer or older, the details may have shifted.
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://github.com/fastly/cli/issues/1037:
- https://github.com/fastly/Viceroy/issues/321
Evidence
Issue gh:fastly/cli#1037: the reporter asked: Issue fastly/cli#1037 (closed, 8 comments): Version Fastly CLI version v10.4.0 (4b869ab3) Built with go version go1.21.0 linux/amd64 Viceroy version: viceroy 0.9.1 What happened This morning, we noticed a new version of Viceroy (0.9.0) seems to have broken our local development environment. I've filed https://github.com/fastly/Viceroy/issues/321 with Viceroy to resolve that. The verified answer was: [Integralist (maintainer)]: Fixed in the Fastly CLI (PR #1039): compute serve was neglecting to install Viceroy's environment files alongside the dependency, which broke the viceroy_version field. Update the Fastly CLI to a release containing that fix and it works again. Evidence thread: https://github.com/fastly/cli/issues/1037
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_CzqPTc10d2lC-zzu__15RQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">The `viceroy_version` field seems to not be working <span>— Vectle</span></a>