Skip to content
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

fix: Allow existingSecret for PostgreSQL and SES email #499

Merged
merged 1 commit into from
Nov 12, 2024

Conversation

hardillb
Copy link
Contributor

fixes #498

Description

Allows for PostgreSQL existingSecret with AWS SES email

Related Issue(s)

#498

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

  • Includes a DB migration? -> add the area:migration label

@hardillb hardillb requested a review from ppawlowski November 12, 2024 14:51
@hardillb hardillb self-assigned this Nov 12, 2024
@hardillb hardillb changed the title Allow existingSecret for PostgreSQL and SES email fix: Allow existingSecret for PostgreSQL and SES email Nov 12, 2024
@ppawlowski ppawlowski merged commit ce3f234 into main Nov 12, 2024
6 of 7 checks passed
@ppawlowski ppawlowski deleted the fix-ses-postgres-existing-secret branch November 12, 2024 15:18
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.

Deploying helm chart with existingSecret set on postgresql.auth and using SES email does not work
2 participants