added modifications for parsing out && and || on front end rule

[sriyer]

The changes to have this implemented for the Consul Catalog are here.

Fixes #1280

[ldez]

Thanks for the contribution 👍

Could you fix this problem:

These files are not properly gofmt'd:
 - provider/consul/consul_catalog.go

Please read CONTRIBUTING.md and run the command make to ensure your code build on your computer.

[sriyer]

The problem is now fixed.

[emilevauge]

@sriyer thanks for your contribution. We think it would be better to both support actual separators and new separators to stay backward compatible. Besides, it would be even better to not be Consul specific and add this new separators in rules.go parseRules. I'm sorry to inform you that therefore I prefer closing this one as we can not merge it. Feel free to contact us if you want some help on this :)

[sriyer]

@emilevauge i'll take a look at rules.go . btw we have this in production already for consul catalog with discovery source being registrator.

[sriyer]

"We think it would be better to both support actual separators and new separators to stay backward compatible" - the change on this pull request supports the use of both. It only replaces || with , and && with ;

[gtrias]

Is there any plan to merge this PR or any alternative workarround to achieve the same funcionality?
I need this feature as well.