Commit 31e38058 authored by katarzyna-z's avatar katarzyna-z

Update from Intelsdi-x pluginsync 0.1.8

parent 3c49aafd
pluginsync_config: '0.1.5'
# File managed by pluginsync
pluginsync_config: '0.1.8'
- .github
- .github/
......@@ -3,9 +3,10 @@
1. [Contributing Code](#contributing-code)
2. [Contributing Examples](#contributing-examples)
3. [Contribute Elsewhere](#contribute-elsewhere)
4. [Thank You](#thank-you)
4. [Reporting Security Issues](#reporting-security-issues)
5. [Thank You](#thank-you)
This repository has dedicated developers from Intel working on updates. The most helpful way to contribute is by reporting your experience through issues. Issues may not be updated while we review internally, but they're still incredibly appreciated.
This repository is primarily **community supported**. We both appreciate and need your contribution to keep it stable. Thank you for being part of the community! We love you for it.
## Contributing Code
**_IMPORTANT_**: We encourage contributions to the project from the community. We ask that you keep the following guidelines in mind when planning your contribution.
......@@ -20,19 +21,20 @@ Once you're ready to contribute code back to this repo, start with these steps:
* Clone the fork to `$GOPATH/src/`:
$ git clone<yourGithubID>/<project>.git
$ cd "${GOPATH}/src/"
$ git clone
* Create a topic branch for your change and checkout that branch:
$ git checkout -b some-topic-branch
$ git checkout -b some-topic-branch
* Make your changes and run the test suite if one is provided.
* Commit your changes and push them to your fork.
* Open a pull request for the appropriate project.
* Contributors will review your pull request, suggest changes, and merge it when it’s ready and/or offer feedback.
If you have questions feel free to contact the [maintainers]( by tagging them: @intelsdi-x/plugin-maintainers.
If you have questions feel free to contact the [maintainers](
## Contributing Examples
The most immediately helpful way you can benefit this project is by cloning the repository, adding some further examples and submitting a pull request.
......@@ -42,5 +44,14 @@ Have you written a blog post about how you use [Snap](
## Contribute Elsewhere
This repository is one of **many** plugins in **Snap**, a powerful telemetry framework. See the full project at
## Reporting Security Issues
The Snap team take security very seriously. If you have any issue regarding security,
please notify us by sending an email to and not by creating a GitHub issue.
We will follow up with you promptly with more information and a plan for remediation.
While we are not offering a security bounty, we would love to send some Snap swag your way along with our
deepest gratitude for your assistance in making Snap a more secure product.
## Thank You
And **thank you!** Your contribution, through code and participation, is incredibly important to us.
......@@ -175,28 +175,3 @@
of your accepting any such warranty or additional liability.
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.
......@@ -35,7 +35,6 @@ go_build=(go build -ldflags "-w")
_info "project path: ${__proj_dir}"
_info "plugin name: ${plugin_name}"
# Disable CGO for builds
export CGO_ENABLED=0
# rebuild binaries:
......@@ -84,7 +84,8 @@ elif [[ $TEST_TYPE == "medium" ]]; then
if [[ -f "${__dir}/" ]]; then
. "${__dir}/"
_info "No medium tests."
elif [[ $TEST_TYPE == "large" ]]; then
if [[ "${TEST_K8S}" != "0" && -f "$__dir/" ]]; then
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment