-
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(inputs.gcs): Google Cloud Storage Input Plugin #8413
Conversation
The error are related with the protobuf update and the ericchiang/k8s@v1.2.0/watch/versioned/generated.pb.go Actually it is described here as an issue. What could be the options? |
I added those lines on a circleci build to highlight the dependency problem (on purpose to highlight the issue, don't want to change the build) Lines 31 to 33 in 98d2403
A google sdk upgrade due to the need of the new protobuf package will have this problem, due to that line ericchiang/k8s#125 |
@gkatzioura sorry no one has responded to you yet, are you still interested in working on this plugin? We recently moved away from ericchiang/k8s to kubernetes/client-go maybe the problem has been resolved in the newer repo? Creating an external plugin as you suggested might be a good option as well. |
Hi @sspaink More than happy! Will spend some time to get back on track. |
Hi @sspaink, seems the issues on the build are resolved. Will do some extra testing. |
!signed-cla |
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.
Thank you for your continued worked on this plugin, you will also need to add a README.md that contains the sample configuration, a description of the plugin, how to use it, etc. The more detail the better.
Hi @sspaink . Did the changes, some renaming and registering the plugin among the other input plugins. |
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.
@gkatzioura thank you for your continued work on this. Recently the Telegraf project changed how the sample configs are maintained, instead of duplicating it in the README.md and the code it is now generated from a single source of truth. I added some suggested changes to help migrate your plugin to use the new structure, hopefully that will make it easy. You will also need to add a file called "sample.conf" that contains the sample configuration.
The input plugin guidelines were updated as well if that makes it more clear: https://github.com/influxdata/telegraf/blob/master/docs/INPUTS.md#input-plugin-guidelines
@gkatzioura do you have time to resolve the conflicts and address the sample config change? No worries if you don't, I wouldn't mind creating a separate pull request to resolve the issues. |
Hi @sspaink checking! |
1a55dce
to
79927e7
Compare
a66007d
to
5de2840
Compare
08d0b3a
to
98bdaf4
Compare
Co-authored-by: Sebastian Spaink <3441183+sspaink@users.noreply.github.com>
Co-authored-by: Sebastian Spaink <3441183+sspaink@users.noreply.github.com>
Co-authored-by: Sebastian Spaink <3441183+sspaink@users.noreply.github.com>
Co-authored-by: Sebastian Spaink <3441183+sspaink@users.noreply.github.com>
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 |
@sspaink all green |
This is a pull request for the issue #8412
Required for all PRs:
How this Telegraf plugin works with Google Cloud Storage
Google Cloud Storage list files in lexicographic order. Files are stored with a date prefix, or their lexicographic order is based on the time the files were created. A GCS crawler will list the files on GCS in order to parse them and submit them to an output. After every Gather execution the last file processed will be stored on GCS as an offset. The next Gather command will continue from that offset.
How Gather works