mirror of
https://github.com/elastic/logstash.git
synced 2025-04-19 20:27:23 -04:00
00e225a849
A pack in this context is a *bundle* of plugins that can be distributed outside of rubygems; it is similar to what ES and kibana are doing, and the user interface is modeled after them. See https://www.elastic.co/downloads/x-pack **Do not mix it with the `bin/logstash-plugin pack/unpack` command.** - it contains one or more plugins that need to be installed - it is self-contains with the gems and the needed jars - it is distributed as a zip file - the file structure needs to follow some rules. - As a reserved name name on elastic.co download http server - `bin/plugin install logstash-mypack` will check on the download server if a pack for the current specific logstash version exist and it will be downloaded, if it doesn't exist we fallback on rubygems. - The file on the server will follow this convention `logstash-mypack-{LOGSTASH_VERSION}.zip` - As a fully qualified url - `bin/plugin install http://test.abc/logstash-mypack.zip`, if it exists it will be downloaded and installed if it does not we raise an error. - As a local file - `bin/plugin install file:///tmp/logstash-mypack.zip`, if it exists it will be installed Fixes #6168
42 lines
464 B
Text
42 lines
464 B
Text
.*.swp
|
|
/*.gem
|
|
logstash*/*.gem
|
|
pkg/*.deb
|
|
pkg/*.rpm
|
|
*.class
|
|
.rbx
|
|
.rbx
|
|
*.tar.gz
|
|
*.jar
|
|
.bundle
|
|
build
|
|
local
|
|
test/setup/elasticsearch/elasticsearch-*
|
|
vendor
|
|
.sass-cache
|
|
data
|
|
.buildpath
|
|
.project
|
|
.DS_Store
|
|
*.pyc
|
|
etc/jira-output.conf
|
|
coverage/*
|
|
.VERSION.mk
|
|
.idea/*
|
|
spec/reports
|
|
rspec.xml
|
|
.install-done
|
|
.vendor
|
|
integration_run
|
|
.mvn/
|
|
qa/.vm_ssh_config
|
|
qa/.vagrant
|
|
qa/acceptance/.vagrant
|
|
qa/Gemfile.lock
|
|
*.ipr
|
|
*.iws
|
|
*.iml
|
|
.gradle
|
|
.idea
|
|
logs
|
|
qa/integration/services/installed/
|