mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 07:01:09 +02:00
8700becc45
* updates api client vars to snake_case for custom messages * updates api client vars to snake_case for tools * updates api client vars to snake_case for sync * updates api client vars to snake_case for secrets engine * updates api client vars to snake_case for auth * updates api client vars to snake_case for usage * updates api client dep to point to gh repo * fixes custom-messages service unit tests * fixes configure-ssh test * fixes configure-ssh test...again
74 lines
3.0 KiB
TypeScript
74 lines
3.0 KiB
TypeScript
/**
|
|
* Copyright (c) HashiCorp, Inc.
|
|
* SPDX-License-Identifier: BUSL-1.1
|
|
*/
|
|
|
|
import Component from '@ember/component';
|
|
import { service } from '@ember/service';
|
|
|
|
import type FlagsService from 'vault/services/flags';
|
|
import type ApiService from 'vault/services/api';
|
|
import type { getUsageDataFunction, UsageDashboardData } from '@hashicorp/vault-reporting/types/index';
|
|
import type { UtilizationReport } from 'vault/usage';
|
|
|
|
/**
|
|
* @module UsagePage
|
|
* @description This component is responsible for fetching usage data and mounting the vault-reporting dashboard view.
|
|
* It uses the `api` service to make a request to the sys/utilization-report endpoint to get the usage data.
|
|
* The data is then processed to replace engine and auth method names with their display names if available.
|
|
* The component also uses the `flags` service to determine if the cluster is HVD managed or not.
|
|
*
|
|
* The logic is self-contained and this component has no args.
|
|
*
|
|
* @example ```js
|
|
* <Usage::Page />
|
|
* ```
|
|
*/
|
|
|
|
export default class UsagePage extends Component {
|
|
@service declare readonly api: ApiService;
|
|
@service declare readonly flags: FlagsService;
|
|
|
|
handleFetchUsageData: getUsageDataFunction = async () => {
|
|
/**
|
|
* We get a partially typed response from the API client, but only 1 level deep.
|
|
* Casting the nested types here and falling back to defaults in the mappings.
|
|
* We should get typescript errors if top level interfaces in the API client or
|
|
* the vault-reporting addon change.
|
|
*/
|
|
const response = (await this.api.sys.generateUtilizationReport()) as UtilizationReport;
|
|
const { lease_count_quotas, replication_status, pki, secret_sync } = response;
|
|
|
|
const data: UsageDashboardData = {
|
|
authMethods: (response.auth_methods as Record<string, number>) || {},
|
|
secretEngines: (response.secret_engines as Record<string, number>) || {},
|
|
leasesByAuthMethod: (response.leases_by_auth_method as Record<string, number>) || {},
|
|
leaseCountQuotas: {
|
|
globalLeaseCountQuota: {
|
|
capacity: lease_count_quotas?.global_lease_count_quota?.capacity || 0,
|
|
count: lease_count_quotas?.global_lease_count_quota?.count || 0,
|
|
name: lease_count_quotas?.global_lease_count_quota?.name || '',
|
|
},
|
|
totalLeaseCountQuotas: lease_count_quotas?.total_lease_count_quotas || 0,
|
|
},
|
|
replicationStatus: {
|
|
drState: replication_status?.dr_state || 'disabled',
|
|
prState: replication_status?.pr_state || 'disabled',
|
|
drPrimary: replication_status?.dr_primary ?? false,
|
|
prPrimary: replication_status?.pr_primary ?? false,
|
|
},
|
|
kvv1Secrets: response.kvv1_secrets || 0,
|
|
kvv2Secrets: response.kvv2_secrets || 0,
|
|
namespaces: response.namespaces || 0,
|
|
pki: {
|
|
totalIssuers: pki?.total_issuers || 0,
|
|
totalRoles: pki?.total_roles || 0,
|
|
},
|
|
secretSync: {
|
|
totalDestinations: secret_sync?.total_destinations || 0,
|
|
},
|
|
};
|
|
return data;
|
|
};
|
|
}
|