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

MM-62533: Improvements for ExternalDBSettings #880

Merged
merged 1 commit into from
Jan 14, 2025
Merged

Conversation

agnivade
Copy link
Member

  • We bump the postgres version to 14.9 as that is the version
    after which "write forwarding" is available on a Global Aurora
    Cluster.
  • We also add the ClusterIdentifier for ExternalDBSettings
    because we need to attach the DB security group to the DB cluster
    like we do for a restored DB backup.

https://mattermost.atlassian.net/browse/MM-62533

- We bump the postgres version to 14.9 as that is the version
after which "write forwarding" is available on a Global Aurora
Cluster.
- We also add the ClusterIdentifier for ExternalDBSettings
because we need to attach the DB security group to the DB cluster
like we do for a restored DB backup.

https://mattermost.atlassian.net/browse/MM-62533
@agnivade agnivade added the 2: Dev Review Requires review by a core committer label Jan 14, 2025
Comment on lines +162 to +167
var identifier string
if t.config.TerraformDBSettings.ClusterIdentifier != "" {
identifier = t.config.TerraformDBSettings.ClusterIdentifier
} else {
identifier = t.config.ExternalDBSettings.ClusterIdentifier
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where I'd love it if Golang could implement some syntactic sugar.

Copy link
Member

@agarciamontoro agarciamontoro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that this applies only when using an AWS cluster, and if you use any other DB, the new ClusterIdentifier can simply be unset. Is that correct?

@agnivade
Copy link
Member Author

I understand that this applies only when using an AWS cluster, and if you use any other DB, the new ClusterIdentifier can simply be unset. Is that correct?

Correct.

@agnivade agnivade merged commit 9314e35 into master Jan 14, 2025
1 check passed
@agnivade agnivade deleted the externalIdentifier branch January 14, 2025 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2: Dev Review Requires review by a core committer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants