@codiac.io/codiac-cli 1.3.246 → 1.3.247
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +163 -163
- package/oclif.manifest.json +1 -1
- package/package.json +1 -1
- package/skill/SKILL.md +26 -0
package/oclif.manifest.json
CHANGED
package/package.json
CHANGED
package/skill/SKILL.md
CHANGED
|
@@ -77,6 +77,32 @@ That's enough to choose the right command and fill it correctly. For depth — t
|
|
|
77
77
|
(`[helm]`/`[env]`/`[label]`/…), dotted-key/escaped-period behavior, `@{...}` templates, CSP
|
|
78
78
|
profiles, the NATS API, and the full hierarchy — read `references/concepts.md`.
|
|
79
79
|
|
|
80
|
+
## Authenticating (you may wake up logged out)
|
|
81
|
+
|
|
82
|
+
You may start **not logged in** — that's expected, and it's your job to get logged in before you
|
|
83
|
+
act. Operating Codiac needs **two** logins:
|
|
84
|
+
- **Codiac** — `cod login` for your tenant (`$CODIAC_TENANT` if it's set in your env; otherwise
|
|
85
|
+
you'll be told which tenant you belong to).
|
|
86
|
+
- **Cloud + registry** — `cod csp login <provider>` for each provider you use (typically `azure`
|
|
87
|
+
for the cluster and `docker` for images).
|
|
88
|
+
|
|
89
|
+
Check first with **`cod whoami`**. If it shows you're not logged in — or any command fails with an
|
|
90
|
+
auth / "not logged in" / "no credentials" error — you're missing one of those logins.
|
|
91
|
+
|
|
92
|
+
**You do not hold these credentials by design.** Never guess, fabricate, or hard-code them, and
|
|
93
|
+
never attempt a deploy/undeploy/config change while unauthenticated. Instead, **ask your operator
|
|
94
|
+
for what you need** — a Codiac login (username + password, or a token) and cloud creds (a login or a
|
|
95
|
+
token per provider) — then authenticate. Read `cod login --help` and `cod csp login --help` for the
|
|
96
|
+
exact accepted forms; both take secrets on stdin so nothing lands in a command string, e.g.:
|
|
97
|
+
|
|
98
|
+
```
|
|
99
|
+
printf '%s' "<password>" | cod login -u <user> --tenantCode "$CODIAC_TENANT" --passwordIn
|
|
100
|
+
cod csp login <provider> # supply the login/token as --help shows (stdin under --silent)
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
Then re-check `cod whoami` and continue. If your session lapses later, you'll see auth errors again
|
|
104
|
+
— ask and re-login the same way.
|
|
105
|
+
|
|
80
106
|
## Running a `cod` command safely
|
|
81
107
|
|
|
82
108
|
1. **Establish context.** Enterprise-scoped commands need a tenant (and often an enterprise).
|