Skip to content

fix(openshift): default RIPTIDE_ENV to 'dev' instead of 'unknown' sentinel #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
trick77 merged 1 commit into from
May 17, 2026
Merged

fix(openshift): default RIPTIDE_ENV to 'dev' instead of 'unknown' sentinel #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions openshift/collector/configmap-app.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,7 @@ metadata:
name: riptide-collector-app
data:
RIPTIDE_LOG_LEVEL: "INFO"
# Stamped on every log record as `env`. Each overlay MUST patch this to
# the real environment ("intg" / "prod"). The "unknown" sentinel makes a
# missing patch loud at first glance in Splunk rather than mis-tagging.
RIPTIDE_ENV: "unknown"
RIPTIDE_ENV: "dev"
RIPTIDE_CONFIG_PATH: "/etc/riptide-collector/riptide.json"
RIPTIDE_TEAM_KEYS_PATH: "/etc/riptide-collector-team-keys/team-keys.json"
RIPTIDE_CONFIG_RELOAD_SECONDS: "30"