Update staging root URL

CHANGELOG.md

@@ -13,6 +13,7 @@
 
 ### Fixed
 
+- Staging root URL updated to `https://stage.taskcluster.nonprod.webservices.mozgcp.net` (the old `cloudops` hostname no longer resolves). Existing configs need updating by hand.
 - `--where` values containing double quotes (e.g. `--where 'name="gcpCredentials"'`, as documented) or commas no longer fail with `bare " in non-quoted-field`. Each `--where` is now taken verbatim; multiple `--where` flags are still ANDed.
 - Raw output mislabelled JSON payloads as `protoPayload`; they are now reported as `jsonPayload`, matching the field paths used in GCP filters (e.g. `jsonPayload.reason` for k8s events). Genuine proto payloads (e.g. audit logs) are still reported as `protoPayload`.
 

README.md

@@ -57,7 +57,7 @@ environments:
     project_id: "moz-fx-webservices-high-nonpro"
     cluster: "webservices-high-nonprod"
     namespace: "taskcluster-stage"
-    root_url: "https://stage.taskcluster.nonprod.cloudops.mozgcp.net"
+    root_url: "https://stage.taskcluster.nonprod.webservices.mozgcp.net"
     key_path: "~/.config/tc-logview/keys/tc-staging.json"
   dev:
     project_id: "taskcluster-dev"
@@ -89,7 +89,7 @@ environments:
     log_bucket: "gke-taskcluster-stage-log-bucket"
     log_location: "global"
     log_view: "_AllLogs"
-    root_url: "https://stage.taskcluster.nonprod.cloudops.mozgcp.net"
+    root_url: "https://stage.taskcluster.nonprod.webservices.mozgcp.net"
 ```
 
 > Tip: `tc-logview auth` prints a summary of all auth modes, the config-init step, and the scoped-token recipe, plus a table of your configured environments.

cmd/config_init.go

@@ -68,7 +68,7 @@ environments:
     project_id: "moz-fx-webservices-high-nonpro"
     cluster: "webservices-high-nonprod"
     namespace: "taskcluster-stage"
-    root_url: "https://stage.taskcluster.nonprod.cloudops.mozgcp.net"
+    root_url: "https://stage.taskcluster.nonprod.webservices.mozgcp.net"
     key_path: "~/.config/tc-logview/keys/tc-staging.json"
   dev:
     project_id: "taskcluster-dev"
@@ -104,7 +104,7 @@ environments:
     log_bucket: "gke-taskcluster-stage-log-bucket"
     log_location: "global"
     log_view: "_AllLogs"
-    root_url: "https://stage.taskcluster.nonprod.cloudops.mozgcp.net"
+    root_url: "https://stage.taskcluster.nonprod.webservices.mozgcp.net"
 `
 		if err := os.WriteFile(cfgPath, []byte(example), 0o644); err != nil {
 			return fmt.Errorf("writing config: %w", err)

plugins/debug-tc-logs/skills/debug-tc-logs/SKILL.md

@@ -56,7 +56,7 @@ The `taskcluster` CLI is a first-class debugging tool for inspecting task state,
 TASKCLUSTER_ROOT_URL=https://community-tc.services.mozilla.com taskcluster ...
 
 # staging
-TASKCLUSTER_ROOT_URL=https://stage.taskcluster.nonprod.cloudops.mozgcp.net taskcluster ...
+TASKCLUSTER_ROOT_URL=https://stage.taskcluster.nonprod.webservices.mozgcp.net taskcluster ...
 ```
 
 ### Key Commands
@@ -139,7 +139,7 @@ Determine the environment from context using this priority:
 3. **TC root URL in message**:
    - `community-tc.services.mozilla.com` → community-tc
    - `firefox-ci-tc.services.mozilla.com` → fx-ci
-   - `stage.taskcluster.nonprod.cloudops.mozgcp.net` → staging
+   - `stage.taskcluster.nonprod.webservices.mozgcp.net` → staging
    - `tc.dev.taskcluster.mozgcp.net` → dev
 4. **workerPoolId prefix**: pool IDs like `proj-*` are typically community-tc; `gecko-*`/`mobile-*` are fx-ci
 5. **If ambiguous**: Ask the user which environment

plugins/debug-tc-logs/skills/debug-tc-logs/examples/task-failure-debugging.md

@@ -7,7 +7,7 @@ Investigation playbook when given a task ID or task URL.
 Parse `tasks/<taskId>` from TC URLs:
 - `https://firefox-ci-tc.services.mozilla.com/tasks/IKBB-zASS_uNES7KC8MJpg` → taskId=`IKBB-zASS_uNES7KC8MJpg`, env=fx-ci
 - `https://community-tc.services.mozilla.com/tasks/...` → env=community-tc
-- `https://stage.taskcluster.nonprod.cloudops.mozgcp.net/tasks/...` → env=staging
+- `https://stage.taskcluster.nonprod.webservices.mozgcp.net/tasks/...` → env=staging
 
 ## 2. Get task status and definition