zinv 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +15 -1
- data/lib/zinv/version.rb +1 -1
- metadata +2 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4c535421a13c6d4073b24e1ac9fe232596f4a981
|
|
4
|
+
data.tar.gz: 300830bd15285c4bb3c4c87ebb270c340f3c82ea
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 1c82d0c48a8dc7b6c63f2df23707b8573186cf7521a3282483e355d32bc460a26c74efa6f6d69ddbf679b9b9e9415bc639f88edb1dc7c4cda4f408f419085929
|
|
7
|
+
data.tar.gz: f84f6f96870327cad8e21a2b8810d3c2dd8577576f688868599bc2f706318818f07476b71b48356c9ecd311940e9c07268e8046b9c540674e190ee7e39819c3f
|
data/README.md
CHANGED
|
@@ -44,6 +44,20 @@ You can insert hosts into the inventory "manually" by setting the following:
|
|
|
44
44
|
In all cases, zinv.rb presumes that the host names it's getting from zabbix (or you, in the case of ZINV_ADD_HOSTS) are resolvable by the host you're running ansible on. Which is to say if you have a host called myhost1, you should be able to ping myhost1 on the ansible machine. The implication is that you've either defined all your host names as fqdns in Zabbix, or you've set up your resolver search list properly.
|
|
45
45
|
|
|
46
46
|
|
|
47
|
+
zinv overloads a couple of the fields in a host definition:
|
|
48
|
+
|
|
49
|
+
You can place the string DONOTMANAGE anywhere in a host's Description field to force zinv to ignore it. If zinv finds DONOTMANAGE in the description, it omits that host from the inventory altogether.
|
|
50
|
+
|
|
51
|
+
You can define host vars in the host's inventory's Notes field. Put yaml in it like:
|
|
52
|
+
|
|
53
|
+
```yaml
|
|
54
|
+
---
|
|
55
|
+
ereiamjh: The ghost in the machine
|
|
56
|
+
kilroy: was here
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
Variables defined in this way will be available to to ansible when it processes the host in question.
|
|
60
|
+
|
|
47
61
|
## Development
|
|
48
62
|
|
|
49
63
|
After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
|
@@ -52,7 +66,7 @@ To install this gem onto your local machine, run `bundle exec rake install`. To
|
|
|
52
66
|
|
|
53
67
|
## Contributing
|
|
54
68
|
|
|
55
|
-
Bug reports and pull requests are welcome on GitHub at https://github.com/
|
|
69
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/svdasein/zinv. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
|
56
70
|
|
|
57
71
|
|
|
58
72
|
## License
|
data/lib/zinv/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: zinv
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Dave Parker
|
|
@@ -121,9 +121,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
121
121
|
version: '0'
|
|
122
122
|
requirements: []
|
|
123
123
|
rubyforge_project:
|
|
124
|
-
rubygems_version: 2.
|
|
124
|
+
rubygems_version: 2.6.11
|
|
125
125
|
signing_key:
|
|
126
126
|
specification_version: 4
|
|
127
127
|
summary: Ansible dynamic inventory script for hosts monitored by zabbix
|
|
128
128
|
test_files: []
|
|
129
|
-
has_rdoc:
|