clickhouse-multi-env-setup
Configures ClickHouse for multiple environments with secrets management and infrastructure-as-code for efficient deployment.
Install this skill
Security score
The clickhouse-multi-env-setup skill was audited on May 30, 2026 and we found 33 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 88 | if (!config) throw new Error(`Unknown environment: ${env}`); |
Template literal with variable interpolation in command context
| 92 | if (!config.password) throw new Error(`CLICKHOUSE_PASSWORD not set for ${env}`); |
Template literal with variable interpolation in command context
| 94 | throw new Error(`ClickHouse ${env} must use HTTPS`); |
Template literal with variable interpolation in command context
| 133 | ```bash |
Template literal with variable interpolation in command context
| 181 | console.log(`Applying ${files.length} schema files to ${env}...`); |
Template literal with variable interpolation in command context
| 187 | console.log(` [OK] ${file}`); |
Template literal with variable interpolation in command context
| 189 | console.error(` [FAIL] ${file}: ${(err as Error).message}`); |
Template literal with variable interpolation in command context
| 204 | throw new Error(`${operation} is blocked in production`); |
Template literal with variable interpolation in command context
| 218 | const expected = `app_${env === 'development' ? 'dev' : env}`; |
Template literal with variable interpolation in command context
| 220 | throw new Error(`Database mismatch: expected ${expected}, got ${database}`); |
Template literal with variable interpolation in command context
| 227 | ```yaml |
Access to .env file
| 59 | password: process.env.CLICKHOUSE_PASSWORD ?? 'dev_password', |
Access to .env file
| 66 | url: process.env.CLICKHOUSE_HOST ?? 'https://staging.clickhouse.cloud:8443', |
Access to .env file
| 67 | username: process.env.CLICKHOUSE_USER ?? 'app_staging', |
Access to .env file
| 68 | password: process.env.CLICKHOUSE_PASSWORD!, |
Access to .env file
| 75 | url: process.env.CLICKHOUSE_HOST!, |
Access to .env file
| 76 | username: process.env.CLICKHOUSE_USER!, |
Access to .env file
| 77 | password: process.env.CLICKHOUSE_PASSWORD!, |
Access to .env file
| 86 | const env = process.env.NODE_ENV ?? 'development'; |
Access to .env file
| 135 | # .env.local (git-ignored) |
Access to .env file
| 177 | const env = process.env.NODE_ENV ?? 'development'; |
Access to .env file
| 203 | if (process.env.NODE_ENV === 'production') { |
Access to .env file
| 217 | const env = process.env.NODE_ENV ?? 'development'; |
External URL reference
| 57 | url: 'http://localhost:8123', |
External URL reference
| 66 | url: process.env.CLICKHOUSE_HOST ?? 'https://staging.clickhouse.cloud:8443', |
External URL reference
| 147 | --secret-string '{"host":"https://prod.clickhouse.cloud:8443","password":"..."}' |
External URL reference
| 155 | echo -n "https://prod.clickhouse.cloud:8443" | \ |
External URL reference
| 162 | host="https://prod.clickhouse.cloud:8443" \ |
External URL reference
| 270 | | TLS error in staging | Using `http://` for Cloud | Force `https://` in non-dev | |
External URL reference
| 276 | - [12-Factor App Config](https://12factor.net/config) |
External URL reference
| 277 | - [ClickHouse Cloud Console](https://clickhouse.cloud/) |
External URL reference
| 278 | - [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) |
External URL reference
| 279 | - [GCP Secret Manager](https://cloud.google.com/secret-manager) |