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

refactor(telegraf): isolate telegraf config service and remove URM interactions #19819

Merged
merged 5 commits into from
Nov 4, 2020

Conversation

GeorgeMac
Copy link
Contributor

@GeorgeMac GeorgeMac commented Oct 26, 2020

Closes #19800

The purpose of this change is to sever the dependency on the URM service from the TelegrafConfigService.
It does need it to function (much like endpoints and rules it misused this service).
This change introduces a new isolated Telegraf package implementation of the service and it removes the behaviors from the *kv.Service implementation.
Further, supporting the work to remove behaviors from the *kv.Service: #19783

UPDATE:

I noticed that I had left a todo to add support for pagination parameters. So I added limit and offset support to find telegrafs.
While doing so, I found it was favorable to update the kv.VisitFunc abstraction to return both an error and now a keep walking bool. So now you return false when you want to stop cursing. This touched a few things, but I believe I got them all. Some places were returning a sentinel error to stay stop walking. I fixed those place to just produce a false (stop walking) response instead.

I deleted both kv and http telegraf config service implementations. Moving us solely to telegraf package imple mentation.

@GeorgeMac GeorgeMac changed the title Isolate Telegraf Config Service (and remove URM interaction) refactor(telegraf): isolate telegraf config service and remove URM interactions Oct 26, 2020
@GeorgeMac GeorgeMac closed this Oct 26, 2020
@GeorgeMac GeorgeMac deleted the gm/telegraf-service branch October 26, 2020 12:25
@GeorgeMac GeorgeMac restored the gm/telegraf-service branch October 26, 2020 13:51
@GeorgeMac
Copy link
Contributor Author

I closed this by accident.

@GeorgeMac GeorgeMac reopened this Oct 26, 2020
@GeorgeMac GeorgeMac force-pushed the gm/telegraf-service branch 2 times, most recently from 13bc0df to 4b51c85 Compare October 26, 2020 14:00
@GeorgeMac GeorgeMac force-pushed the gm/notification-endpoints-service branch 4 times, most recently from f0c3c82 to c94f478 Compare October 27, 2020 12:31
Base automatically changed from gm/notification-endpoints-service to master October 28, 2020 15:22
@GeorgeMac GeorgeMac force-pushed the gm/telegraf-service branch from 4b51c85 to b82e2ca Compare October 29, 2020 16:42
@GeorgeMac GeorgeMac marked this pull request as ready for review October 29, 2020 16:44
@GeorgeMac GeorgeMac requested review from a team and brettbuddin and removed request for a team October 29, 2020 16:45
feat(dashboard): add owner ID to dashboard model

This adds the explicit OwnerID field to Dashboard and also adds a
migration which populates dashboard owners IDs based on dashboard owner
URMs.

feat(dashboards): isolate service in own package

This change isolates the dashboards service into its own package. It
also updates the API to no longer interface with user resource mappings.
Instead it defines new handlers which rely on the newly populated owner
ID field.

chore(dashboards): port tests from http package into new service transport package

chore(launcher): use dashboard transport package client in launcher tests

chore(kv): remove now defunkt dashboard service implementations
@GeorgeMac GeorgeMac merged commit 8ca2989 into master Nov 4, 2020
@GeorgeMac GeorgeMac deleted the gm/telegraf-service branch November 4, 2020 15:53
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

Successfully merging this pull request may close these issues.

Move Telegraf service into own package
2 participants