Allow opt. space between device-id and colon.

[roderickm]

fix #2101

[elasticsearch-release]

Can one of the admins verify this patch?

[wiibaa]

@roderickm as 1.5 will use exploded projects/gems, could you please move your PR to https://github.com/logstash-plugins/logstash-patterns-core

[roderickm]

@wiibaa New PR created at logstash-plugins/logstash-patterns-core#2

[suyograo]

@roderickm Can you please sign the CLA? https://github.com/elasticsearch/logstash/blob/master/CONTRIBUTING.md#contribution-steps

[roderickm]

CLA signed.

[roderickm]

The CLA Check is failing despite my signing it over a week ago.

This issue report and contribution were done on my employers' time. After my employer submitted the CLA as a company wanting employees to contribute, I signed the CLA last week using my work address. However, my personal address the primary one on my github account. Perhaps the cla_check verifies only the primary github email address?

[untergeek]

Yes, the check depends on your github account email.

—Aaron

On Thu, Jan 15, 2015 at 8:52 AM, roderickm notifications@github.com
wrote:

The CLA Check is failing despite my signing it over a week ago.
This issue report and contribution were done on my employers' time. After my employer submitted the CLA as a company wanting employees to contribute, I signed the CLA last week using my work address. However, my personal address the primary one on my github account. Perhaps the cla_check verifies only the primary github email address?

Reply to this email directly or view it on GitHub:
#2102 (comment)

[roderickm]

Thanks, @untergeek. To be clear, the work email address with which I signed the CLA is a secondary address on my github account.

[jordansissel]

For Logstash 1.5.0, we've moved all plugins (and grok patterns) to individual repositories. Can you move this pull request to https://github.com/logstash-plugins/logstash-patterns-core?

This sequence of steps may help you do this migration:

1. Fork this repository

2. Clone your fork

   git clone https://github.com/roderickm/logstash.git

3. Create a branch:

   git checkout -b my-branch-name

4. Apply the patches from this PR into your branch:

   curl -s https://github.com/elastic/logstash/pull/2102.patch | git am

   This should take your commits from this PR and commit them to your new local branch.

5. Push!

   git push origin my-branch-name

6. Open a new PR against https://github.com/logstash-plugins/logstash-patterns-core

7. Sign the CLA

   Our CLA check indicates that some commit authors have not signed the CLA or are not members of Elasticsearch. See our contributor agreement for more details. :)