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

Another resync oddity #9

Open
hellertime opened this issue Jul 10, 2015 · 2 comments
Open

Another resync oddity #9

hellertime opened this issue Jul 10, 2015 · 2 comments

Comments

@hellertime
Copy link

So I was testing out the new code and noticed something interesting.

To test, I cleared the consul kv tree of marathon data. Then restarted marathon-consul, the kv tree got repopulated, except there were no 'taskStatus' values, as these only are provided by marathon on Status Update events.

Unfortunately I had been using the taskStatus to determine if I would add a record to my service config or not, and since the taskStatus field was empty, nothing was added (well it was, but commented out).

So it appears that resync works, the apps were repopulated in consul, but the taskStatus will not change until restarting the app.

@BrianHicks
Copy link
Contributor

Thanks for reporting. We're gonna have to do something creative here, as the task struct fetched through the API is a different shape than the task struct received from the event stream.

@scalp42
Copy link

scalp42 commented Nov 11, 2015

@hellertime are you using consul-template ? If yes, do you mind sharing an example ?

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

3 participants