@checkstack/anomaly-frontend 0.6.0 → 0.6.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,54 @@
|
|
|
1
1
|
# @checkstack/anomaly-frontend
|
|
2
2
|
|
|
3
|
+
## 0.6.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- Updated dependencies [e819276]
|
|
8
|
+
- @checkstack/healthcheck-frontend@0.29.0
|
|
9
|
+
|
|
10
|
+
## 0.6.1
|
|
11
|
+
|
|
12
|
+
### Patch Changes
|
|
13
|
+
|
|
14
|
+
- 0cac684: Align the health-check run-history gates end to end. The history surfaces had a
|
|
15
|
+
three-way drift: the route allowed `configuration.read`, the page required
|
|
16
|
+
manage capability, and the procedures required the standalone
|
|
17
|
+
`healthcheck.details` rule - so global read-rule holders reached a page that
|
|
18
|
+
denied them, and team-scoped managers passed the page gate but got 403s from
|
|
19
|
+
every data call.
|
|
20
|
+
|
|
21
|
+
Detailed run history is now a MANAGER surface everywhere, with system owners
|
|
22
|
+
included: access requires global `configuration.manage`, a team manage grant
|
|
23
|
+
on the CONFIGURATION, or manage access to the SYSTEM - a system's owning team
|
|
24
|
+
sees every run of that system, whoever owns the configuration.
|
|
25
|
+
|
|
26
|
+
- Routes, pages, drawer links, and the anomaly/health signals gate on the
|
|
27
|
+
manage capability (with `catalog.system` as the parent type); the drawer and
|
|
28
|
+
chart hook check the caller's grant on the specific configuration OR system.
|
|
29
|
+
- All three history procedures (`getDetailedHistory`,
|
|
30
|
+
`getDetailedAggregatedHistory`, `getRunById`) are authorized in the handler
|
|
31
|
+
via a shared fail-closed module (`history-access.ts`) - the triple-OR is not
|
|
32
|
+
expressible with the declarative instanceAccess modes. `getRunById`
|
|
33
|
+
authorizes against the fetched run's own configuration/system, and answers
|
|
34
|
+
`undefined` for unauthorized callers so run ids don't leak existence.
|
|
35
|
+
- The feed (`getDetailedHistory`) scopes team callers to runs of their
|
|
36
|
+
configurations UNION runs of their systems, with correct pagination totals.
|
|
37
|
+
|
|
38
|
+
BREAKING CHANGES:
|
|
39
|
+
|
|
40
|
+
- The standalone `healthcheck.details` access rule is REMOVED. Roles that held
|
|
41
|
+
`details` without `configuration.manage` lose access to detailed run data;
|
|
42
|
+
grant them the manage rule (or a team grant on the configuration/system)
|
|
43
|
+
instead. Stale role rows referencing the removed rule are inert.
|
|
44
|
+
- `getDetailedAggregatedHistory` is `authenticated` (was `public`); anonymous
|
|
45
|
+
callers could never pass its access rule anyway.
|
|
46
|
+
|
|
47
|
+
- Updated dependencies [0cac684]
|
|
48
|
+
- @checkstack/healthcheck-common@1.11.0
|
|
49
|
+
- @checkstack/healthcheck-frontend@0.28.0
|
|
50
|
+
- @checkstack/notification-frontend@0.7.1
|
|
51
|
+
|
|
3
52
|
## 0.6.0
|
|
4
53
|
|
|
5
54
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@checkstack/anomaly-frontend",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.2",
|
|
4
4
|
"license": "Elastic-2.0",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"sideEffects": [
|
|
@@ -20,10 +20,10 @@
|
|
|
20
20
|
"@checkstack/catalog-common": "2.6.0",
|
|
21
21
|
"@checkstack/common": "0.19.0",
|
|
22
22
|
"@checkstack/frontend-api": "0.13.0",
|
|
23
|
-
"@checkstack/healthcheck-common": "1.
|
|
24
|
-
"@checkstack/healthcheck-frontend": "0.
|
|
23
|
+
"@checkstack/healthcheck-common": "1.11.0",
|
|
24
|
+
"@checkstack/healthcheck-frontend": "0.29.0",
|
|
25
25
|
"@checkstack/notification-common": "1.5.0",
|
|
26
|
-
"@checkstack/notification-frontend": "0.7.
|
|
26
|
+
"@checkstack/notification-frontend": "0.7.1",
|
|
27
27
|
"@checkstack/signal-frontend": "0.3.2",
|
|
28
28
|
"@checkstack/ui": "1.22.0",
|
|
29
29
|
"date-fns": "^4.4.0",
|
|
@@ -60,8 +60,10 @@ export const AnomalySignalsFiller: React.FC<Props> = ({
|
|
|
60
60
|
systemId: row.systemId,
|
|
61
61
|
configurationId: row.configurationId,
|
|
62
62
|
}),
|
|
63
|
-
// The history detail page is
|
|
64
|
-
accessRule
|
|
63
|
+
// The history detail page is a manager surface; render as text for
|
|
64
|
+
// users without global healthcheck manage (a signal's accessRule is a
|
|
65
|
+
// global check - team-scoped managers reach history via their pages).
|
|
66
|
+
accessRule: healthCheckAccess.configuration.manage,
|
|
65
67
|
});
|
|
66
68
|
}, [confirmed, suspicious, systemIds]);
|
|
67
69
|
|