You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reports whether the project is attached to a team, and surfaces
`zitadel claim` in the advisory when it is not.
Always a warning, never a failure. An unattached project works exactly
like an attached one, same issuer, same users, same applications, so the
only thing missing is durability and that is the developer's call rather
than a defect. It matters mechanically too: `doctor` turns any `fail`
into a thrown `E_VALIDATION`, so failing here would break every scripted
`zitadel doctor` run against a project nobody had claimed yet.
Implements `SanityCheck` directly rather than extending the abstract
base, for the same reason `ManagedFilesCheck` does: the base's
verify-throws contract can only express pass or fail. That also means
nothing wraps a throw from `run`, so an unreadable secret or config is
caught and reported as a skip. Otherwise a missing `.zitadel/secret`
would crash the whole battery on a nudge and hide the `secret` check that
actually reports the problem, with its repair path.
`fix` stays the inherited no-op. `doctor --fix` calls it on every
non-passing check, but a claim needs a human to sign in through a
browser, so there is nothing safe to automate.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments