Skip to content

fix: hardcoded redshift secret name #9

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.

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

Conversation

raykrishardi
Copy link
Contributor

@raykrishardi raykrishardi commented Jul 9, 2025

if you try to create 2 redshift using this component, secrets manager will throw an error since you try to create a secret that already exists (i.e. has the same name)

error

Resource handler returned message: "The operation failed because the secret SecretRedshiftMasterUser already exists. (Service: SecretsManager, Status Code: 400, Request ID: d37aeb09-24a6-4bb9-ace7-e16fb030c378) (SDK Attempt Count: 1)" (RequestToken: 395e1218-e2c7-599c-926f-e030bae3e4fd, HandlerErrorCode: AlreadyExists)

@raykrishardi raykrishardi changed the title feat: custom redshift secret name to fix issue when there are 2 redshifts deployed using highlander fix: custom redshift secret name to fix issue when there are 2 redshifts deployed using highlander Jul 9, 2025
@raykrishardi raykrishardi changed the title fix: custom redshift secret name to fix issue when there are 2 redshifts deployed using highlander fix: hardcoded redshift secret name Jul 9, 2025
@tarunmenon95 tarunmenon95 merged commit 60b7035 into theonestack:main Jul 10, 2025
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants