fluent-plugin-vmware-loginsight 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +7 -0
  2. data/.gitignore +5 -0
  3. data/CONTRIBUTING.md +83 -0
  4. data/README.md +50 -0
  5. metadata +109 -0
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 7677f5c4289ba3ecb32f9aa6ddc35c6b8f70f4b6
4
+ data.tar.gz: 73023509bb66d43595176f3625256009e4187cac
5
+ SHA512:
6
+ metadata.gz: d3662938668a3307722b0ac604186cfc7a1b397c18d16968cd669360fd2a5c148c4d7904547d9a7258abda2818cbce2a8ee1505206259120e9efb0955f109bcb
7
+ data.tar.gz: 12c29d1640c720f3b380475d3fd2f9e368817d3b5e794ad14960120c0ba6d70ab789764b64737eb28dcbdafed382af331a700499b0f18400b3d93f1f50ae4ec3
data/.gitignore ADDED
@@ -0,0 +1,5 @@
1
+ *.gem
2
+ *.rbc
3
+ .bundle
4
+ .config
5
+ Gemfile.lock
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,83 @@
1
+
2
+
3
+ # Contributing to fluent-plugin-vmware-loginsight
4
+
5
+ The fluent-plugin-vmware-loginsight project team welcomes contributions from the community. If you wish to contribute code and you have not
6
+ signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any
7
+ questions about the CLA process, please refer to our [FAQ](https://cla.vmware.com/faq).
8
+
9
+ ## Community
10
+
11
+ ## Getting Started
12
+
13
+ ## Contribution Flow
14
+
15
+ This is a rough outline of what a contributor's workflow looks like:
16
+
17
+ - Create a topic branch from where you want to base your work
18
+ - Make commits of logical units
19
+ - Make sure your commit messages are in the proper format (see below)
20
+ - Push your changes to a topic branch in your fork of the repository
21
+ - Submit a pull request
22
+
23
+ Example:
24
+
25
+ ``` shell
26
+ git remote add upstream https://github.com/vmware/fluent-plugin-vmware-loginsight.git
27
+ git checkout -b my-new-feature master
28
+ git commit -a
29
+ git push origin my-new-feature
30
+ ```
31
+
32
+ ### Staying In Sync With Upstream
33
+
34
+ When your branch gets out of sync with the vmware/master branch, use the following to update:
35
+
36
+ ``` shell
37
+ git checkout my-new-feature
38
+ git fetch -a
39
+ git pull --rebase upstream master
40
+ git push --force-with-lease origin my-new-feature
41
+ ```
42
+
43
+ ### Updating pull requests
44
+
45
+ If your PR fails to pass CI or needs changes based on code review, you'll most likely want to squash these changes into
46
+ existing commits.
47
+
48
+ If your pull request contains a single commit or your changes are related to the most recent commit, you can simply
49
+ amend the commit.
50
+
51
+ ``` shell
52
+ git add .
53
+ git commit --amend
54
+ git push --force-with-lease origin my-new-feature
55
+ ```
56
+
57
+ If you need to squash changes into an earlier commit, you can use:
58
+
59
+ ``` shell
60
+ git add .
61
+ git commit --fixup <commit>
62
+ git rebase -i --autosquash master
63
+ git push --force-with-lease origin my-new-feature
64
+ ```
65
+
66
+ Be sure to add a comment to the PR indicating your new changes are ready to review, as GitHub does not generate a
67
+ notification when you git push.
68
+
69
+ ### Code Style
70
+
71
+ ### Formatting Commit Messages
72
+
73
+ We follow the conventions on [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/).
74
+
75
+ Be sure to include any related GitHub issue references in the commit message. See
76
+ [GFM syntax](https://guides.github.com/features/mastering-markdown/#GitHub-flavored-markdown) for referencing issues
77
+ and commits.
78
+
79
+ ## Reporting Bugs and Creating Issues
80
+
81
+ When opening a new issue, try to roughly follow the commit message format conventions above.
82
+
83
+ ## Repository Structure
data/README.md ADDED
@@ -0,0 +1,50 @@
1
+ # fluent-plugin-vmware-loginsight
2
+
3
+ ## Overview
4
+ output plugin to do forward logs to VMware Log Insight
5
+
6
+ ## Installation
7
+
8
+ ### RubyGems
9
+
10
+ ```
11
+ $ gem install fluent-plugin-vmware-loginsight
12
+ ```
13
+
14
+ ### Bundler
15
+
16
+ Add following line to your Gemfile:
17
+
18
+ ```ruby
19
+ gem "fluent-plugin-vmware-loginsight"
20
+ ```
21
+
22
+ And then execute:
23
+
24
+ ```
25
+ $ bundle
26
+ ```
27
+
28
+ ## Configuration
29
+
30
+ You can generate configuration template:
31
+
32
+ ```
33
+ $ fluent-plugin-config-format output vmware-loginsight
34
+ ```
35
+
36
+ You can copy and paste generated documents here.
37
+
38
+ ## Documentation
39
+
40
+ ## Releases & Major Branches
41
+
42
+ ## Contributing
43
+
44
+ The fluent-plugin-vmware-loginsight project team welcomes contributions from the community. If you wish to contribute code and you have not
45
+ signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any
46
+ questions about the CLA process, please refer to our [FAQ](https://cla.vmware.com/faq). For more detailed information,
47
+ refer to [CONTRIBUTING.md](CONTRIBUTING.md).
48
+
49
+ ## License
50
+
metadata ADDED
@@ -0,0 +1,109 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: fluent-plugin-vmware-loginsight
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.0
5
+ platform: ruby
6
+ authors:
7
+ - Vishal Mohite
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain: []
11
+ date: 2018-08-13 00:00:00.000000000 Z
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: bundler
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: '1.14'
20
+ type: :development
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: '1.14'
27
+ - !ruby/object:Gem::Dependency
28
+ name: rake
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: '12.0'
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: '12.0'
41
+ - !ruby/object:Gem::Dependency
42
+ name: test-unit
43
+ requirement: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - "~>"
46
+ - !ruby/object:Gem::Version
47
+ version: '3.0'
48
+ type: :development
49
+ prerelease: false
50
+ version_requirements: !ruby/object:Gem::Requirement
51
+ requirements:
52
+ - - "~>"
53
+ - !ruby/object:Gem::Version
54
+ version: '3.0'
55
+ - !ruby/object:Gem::Dependency
56
+ name: fluentd
57
+ requirement: !ruby/object:Gem::Requirement
58
+ requirements:
59
+ - - ">="
60
+ - !ruby/object:Gem::Version
61
+ version: 0.14.10
62
+ - - "<"
63
+ - !ruby/object:Gem::Version
64
+ version: '2'
65
+ type: :runtime
66
+ prerelease: false
67
+ version_requirements: !ruby/object:Gem::Requirement
68
+ requirements:
69
+ - - ">="
70
+ - !ruby/object:Gem::Version
71
+ version: 0.14.10
72
+ - - "<"
73
+ - !ruby/object:Gem::Version
74
+ version: '2'
75
+ description: Fluend output plugin to forward logs to VMware Log Insight
76
+ email:
77
+ - vmohite@vmware.com
78
+ executables: []
79
+ extensions: []
80
+ extra_rdoc_files: []
81
+ files:
82
+ - ".gitignore"
83
+ - CONTRIBUTING.md
84
+ - README.md
85
+ homepage: https://github.com/vmware/fluent-plugin-vmware-loginsight
86
+ licenses:
87
+ - MIT
88
+ metadata: {}
89
+ post_install_message:
90
+ rdoc_options: []
91
+ require_paths:
92
+ - lib
93
+ required_ruby_version: !ruby/object:Gem::Requirement
94
+ requirements:
95
+ - - ">="
96
+ - !ruby/object:Gem::Version
97
+ version: '0'
98
+ required_rubygems_version: !ruby/object:Gem::Requirement
99
+ requirements:
100
+ - - ">="
101
+ - !ruby/object:Gem::Version
102
+ version: '0'
103
+ requirements: []
104
+ rubyforge_project:
105
+ rubygems_version: 2.5.2.3
106
+ signing_key:
107
+ specification_version: 4
108
+ summary: Fluend output plugin to forward logs to VMware Log Insight
109
+ test_files: []