mirror of
https://github.com/Unleash/unleash.git
synced 2025-01-31 00:16:47 +01:00
1897f8a19d
This PR adds connected environments to the project status payload. It's done by: - adding a new `getConnectedEnvironmentCountForProject` method to the project store (I opted for this approach instead of creating a new view model because it already has a `getEnvironmentsForProject` method) - adding the project store to the project status service - updating the schema For the schema, I opted for adding a `resources` property, under which I put `connectedEnvironments`. My thinking was that if we want to add the rest of the project resources (that go in the resources widget), it'd make sense to group those together inside an object. However, I'd also be happy to place the property on the top level. If you have opinions one way or the other, let me know. As for the count, we're currently only counting environments that have metrics and that are active for the current project. |
||
|---|---|---|
| .. | ||
| access | ||
| api-tokens | ||
| change-request-access-service | ||
| change-request-segment-usage-service | ||
| client-feature-toggles | ||
| dependent-features | ||
| events | ||
| export-import-toggles | ||
| feature-lifecycle | ||
| feature-naming-pattern | ||
| feature-search | ||
| feature-toggle | ||
| frontend-api | ||
| group | ||
| instance-stats | ||
| integration-events | ||
| maintenance | ||
| metrics | ||
| onboarding | ||
| personal-dashboard | ||
| playground | ||
| private-project | ||
| project | ||
| project-environments | ||
| project-insights | ||
| project-status | ||
| scheduler | ||
| segment | ||
| tag-type | ||
| traffic-data-usage | ||
| ui-observability-controller | ||
| user-subscriptions | ||
| index.ts | ||