Problem
pushkin aws init regenerates random passwords on every run, causing authentication failures when resources already exist.
Current Behavior
- First run: Creates RabbitMQ with password
abc123
- Second run: Generates NEW password
xyz789, updates task definitions
- RabbitMQ container still expects
abc123 but API tries xyz789 → Auth failure
- Same issue with RDS database passwords during migrations
Cause
Line 1817 in aws/index.js/ecsTaskCreator(): (RabbitMQ)
const rabbitPW = Math.random().toString(); // Always generates new password
Line 1199 in aws/index.js/initDb(): (RDS database)
dbPassword = generateSecurePassword(); // Always generates new password
But there are no check for existing passwords in pushkin.yaml
Wanted Behavior
- Resource exist + password in
pushkin.yaml → reuse
- Resource don't exist → generate new password and update
pushkin.yaml
Extra enhancements
- Use
crypto.randomBytes() for password generation instead of Math.random() for both
Problem
pushkin aws initregenerates random passwords on every run, causing authentication failures when resources already exist.Current Behavior
abc123xyz789, updates task definitionsabc123but API triesxyz789→ Auth failureCause
Line 1817 in
aws/index.js/ecsTaskCreator(): (RabbitMQ)Line 1199 in
aws/index.js/initDb(): (RDS database)But there are no check for existing passwords in
pushkin.yamlWanted Behavior
pushkin.yaml→ reusepushkin.yamlExtra enhancements
crypto.randomBytes()for password generation instead ofMath.random()for both