Skip to content

Conversation

@nickgerace
Copy link
Contributor

No description provided.

@github-actions
Copy link

github-actions bot commented Jan 21, 2026

Dependency Review

✅ No vulnerabilities or OpenSSF Scorecard issues found.

Scanned Files

None

@nickgerace nickgerace force-pushed the nick/3adcc0a branch 2 times, most recently from c652fb0 to bd4b528 Compare January 22, 2026 23:38
This changes allows innit to take in env variables. This can be
configured by environment variable or command line argument with the
new "mode" type. It contains two variants: "env" and "ssm". If the mode
is not provided, it defaults to "ssm", which ensures innit runs as it
does on main today. If "env" is provided, then innit will take in
environment variables to configure all services rather than using ssm.

The environment variable use case may not be that interesting on its
own, but innit being able to be used across several verticals and cloud
providers in the future helps standardize the SI initialization
procedure. Theorhetically, a secrets manager provided by a helm chart
on a k8s cluster can do the same thing. For now, innit's env var use
case is valuable. We'll see how long that will remain to be the case.

Signed-off-by: Nick Gerace <nick@systeminit.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants