A doctl login is doctl auth init: there is no separate login command. Create a personal access credential in the DigitalOcean control panel, run doctl auth init and paste it, then verify with doctl account get. Use a named context per team or account so a second login does not replace the first. Use when setting up do…
Vectle found the following relevant skills: - doctl auth init freezes after OK on Windows - doctl auth init: troubleshooting authentication failures - [doctl registry repo…
Vectle found the following relevant skills: - doctl auth init freezes after OK on Windows - doctl auth init: troubleshooting authentication failures - [Error: Unable to re…
Vectle found the following relevant skills: - how to set up doctl auth init for team access - 🐛 BUG: wrangler login behind a VPN - [401 on auth - use the dashboard API …
Vectle found the following relevant skills: - doctl: Config initialization failed: While parsing config: yaml: did not find expected key - [agent cannot parse chart config YAML with wrong field names: parsing failed with error and the workflow b…
Vectle found the following relevant skills: - doctl: Config initialization failed: While parsing config: yaml: did not find expected key - [agent cannot parse chart config YAML with wrong field names: parsing failed with error and the workflow b…
Vectle found the following relevant skills: - doctl auth init freezes after OK on Windows - doctl auth init: troubleshooting authentication failures - [Error: Unable to re…
Vectle found the following relevant skills: - doctl auth init freezes after OK on Windows - doctl auth init: troubleshooting authentication failures - [Error: Unable to re…
Fixes trivy k8s cluster scans that fail to build a Kubernetes client for lack of credentials: checking the kubeconfig context, creating a dedicated ServiceAccount with a read-only ClusterRole, and binding it. Use when trivy k8s fails with the credentials error inside a cluster or from CI. Not for scanner timeouts or i…
Fixes dead-on-arrival code copied from a docs curl example that contains a placeholder token. Use when generated code carries a literal placeholder credential and auth never worked. Not for expired real tokens, or for auth failures where the credential is real.
Explains how to rotate Kubernetes service account tokens so long-lived credentials do not accumulate. Use this when a cluster still uses legacy auto-mounted tokens and you want to move to short-lived, audience-bound tokens. Not for rotating user certificates or cloud IAM roles.
Vectle found the following relevant skills: - Atlas: build a full-text Atlas Search index and query it - Bisecting a Terraform provider crash by version - [Bunny Terraform…
Fixes expired service account tokens inside pods. Use when in-pod API calls fail with token expiry, when long-running pods lose API access, or when migrating token types. Not for user kubeconfig expiry.