* chore: alphabetize root reducer
* refactor(norm): normalize authorizations (tokens)
* refactor: orgs use immer and reducer helpers
* fix: provide initial state to orgs reducer
* fix(auth): normalize auths on token creation
* fix: initial state with empty object
The storage engine isn't capable of sending back empty tables when a
series is empty. Because of this, we disable the push down and let flux
do the filtering in the case where there is a filter and it is specified
to keep the empty tables.
* feat(norm): separate action creators and thunks
* feat(norm): wip normalize buckets
* refactor(norm): change consumption of buckets to norm shape
* test(ui/getResources): change test to accept norm shape
* test(buckets): fix runtime error
* refactor: use immer produce in members reducer
* refactor(norm): normalize organizations
* chore: add junit.xml to gitignore
* test(norm): restructure tests to conform to normalized orgs
* fix: set proper org in local storage
* fix: update createTelegraf to use types
* fix: runtime error when adding telegraf configs
* fix: dashboard thunk not using new org shape
* chore: move edit org to correct place
* fix(orgs): faulty reducer logic
* feat(ui): Add matching rules card to alert builder
* feat(checks): Add tags from query results to NR matching query parameters
* feat(ui): Update changelog
* feat(nr): Change api function to match import convention
* fix(ui): Fix changelog update mistake
* Click submit button after typing in time machine
* feat(notification rules): Add feature flag to matching notification rules
* feat(checks): Add custom check type
* feat(checks): Remove alert builder from custom check
* feat(checks): Add AlertBuilderAction to list of possible actions
* feat(checks): Query visualization does not make sense for custom check
* feat(check): check editor should only reexecute queries if view query changes
* Update ui/src/timeMachine/components/TimeMachineFluxEditor.tsx
Co-Authored-By: Bucky Schwarz <hoorayimhelping@users.noreply.github.com>
* Address PR review
Co-authored-by: Bucky Schwarz <hoorayimhelping@users.noreply.github.com>
issue here is that the unique by name index for variables was implemented
and has the same functionality about it that this orgs index has. The duplicative
orgs index was nuked. The migration to hydrate the org/name index never
happened. This is a stop gap until that migration is in place.
this is work moving us towards more reusable components that add some
rigidity around handling indexes and the entity bucket. The behavior
is very common across much of the kv pkg. This can be reused throughout.
adding some easy wins for tracing(eventually metrics) that enable more
insight that what is currently possible. It normalizes these concerns
across the kv store.
With `/health`, it is possible to override the overall status reported.
This change adds the same functionality to `/ready`. This allows
incident responders to take an unhealthy pod out of a service without
killing it—giving them time to gather meaningful forensic data from the
pod. The new contract is:
Force not ready:
GET /ready?force=true&ready=false
Force ready:
GET /ready?force=true&ready=true
Disable override:
GET /ready?force=false
feat(ui): added last run status checks for notification rules and check rules, readded updateCheck to fix linter and functionality issues with program and added tests to ensure check creation and update stability