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

Remove support for Cassandra-backed Kong #974

Merged
merged 1 commit into from
Dec 7, 2020
Merged

Conversation

rainest
Copy link
Contributor

@rainest rainest commented Dec 4, 2020

What this PR does / why we need it:
Cassandra-backed Kong instance support is going away in 1.1.0 after being deprecated in 0.9.0. This replaces the deprecation warning with a fatal error

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #968

@rainest rainest added this to the 1.1.0 milestone Dec 4, 2020
@@ -282,8 +282,8 @@ func main() {
controllerConfig.Kong.InMemory = true
}
if kongDB == "cassandra" {
log.Warn("running controller with kong cassandra as a datastore is deprecated; " +
"please consider using postgres or in-memory mode")
log.Fatalf("Cassandra-backed deployments of Kong managed by the ingress controller are no longer supported;" +
Copy link
Member

Choose a reason for hiding this comment

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

Nit: all errors should start with lower case letter.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should be fine here--guidance is that it's fine if the leading word is a proper noun, and Cassandra is: https://github.com/golang/go/wiki/CodeReviewComments#error-strings

@rainest rainest merged commit fd6e3a3 into next Dec 7, 2020
@rainest rainest deleted the feat/no-cassandra branch December 7, 2020 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants