-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat(outputs.postgresql): add Postgresql output #11672
Conversation
81da34e
to
a149806
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the all.go issue this looks good to me
plugins/outputs/all/all.go
Outdated
@@ -1 +1,62 @@ | |||
package all | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is restoring all the output plugin imports. The PR also adds a separate postgresql.go import file here so I think we can get rid of this and it will continue to be imported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah good catch, fixed
Functionally, this is the same as influxdata#8651. The differences are two fold right now: 1) tests all use test-containers and right now do not have the ability to use a local postgresql database 2) The tests expecting pguint extension will skip untill the testcontainer startup installs that extension.
a6c0626
to
f1307d1
Compare
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
Functionally, this is the same as #8651. The differences are two fold
right now:
to use a local postgresql database
test-container startup installs that extension.
closes: #3428
closes: #3408