Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plans for ttl? #3

Open
blackside opened this issue Mar 2, 2017 · 1 comment
Open

Any plans for ttl? #3

blackside opened this issue Mar 2, 2017 · 1 comment

Comments

@blackside
Copy link

Just curious to know if you are planning to do something more with this registrator?
For example the -ttl functionality of the original registrator?

@cabrinoob
Copy link
Owner

Why not. It depends of how much time I can allocate to this. The last functionality I worked on is the possibility to add metadata to the K/V store of consul at the same time you register the service.

I created a new label SERVICE_XXX_ROUTE_PATH[BEG|REG] which allows me to generate ACLs and backend in HAProxy through consul-template. This functionnality needs to be deeper tested before I merge it.

But for the TTL, why not. It's not a functionnality I used with the original registrator. I have to take a look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants