cleanup
This commit is contained in:
@@ -22,6 +22,5 @@ export const generatedAPI = rawAPI.enhanceEndpoints({
|
||||
return originalQuery(requestOptions);
|
||||
};
|
||||
},
|
||||
// todo - do i add data massaging to list correlations here??
|
||||
},
|
||||
});
|
||||
|
||||
@@ -6,19 +6,6 @@ import { CorrelationData, CorrelationExternal, CorrelationQuery } from '@grafana
|
||||
|
||||
import { toEnrichedCorrelationData } from './useCorrelations';
|
||||
|
||||
/*
|
||||
the various todos in this function relate to some changes that were required for correlations to be added to app platform
|
||||
we now must resolve those changes with the way correlations currently functions
|
||||
the main one is around the various source/target references - current this just refers to datasources by UID, but I was
|
||||
required to do a group/name combination - how do I resolve this?
|
||||
|
||||
secondly, I was required to remove the provisioned flag. This provisioned flag locks the correlations record and makes it readonly
|
||||
so people don't make edits that will be overwritten by provisioned correlations. Maybe this isn't relevant for app platform and hardcoding it to false is fine.
|
||||
|
||||
With transformations, I just didn't convert because they should be straightforward, that can be ignored for now and I'll work on it
|
||||
|
||||
also, maybe this should be closer to the app platform code, like in the client code? any other best practices?
|
||||
*/
|
||||
export const toEnrichedCorrelationDataK8s = (item: CorrelationK8s): CorrelationData | undefined => {
|
||||
if (item.metadata.name !== undefined) {
|
||||
const baseCor = {
|
||||
|
||||
@@ -42,17 +42,3 @@ developer_mode = true ; Enable developer mode to use in-memory implementations o
|
||||
[secrets_manager]
|
||||
run_secrets_db_migrations = true
|
||||
run_data_key_migration = true
|
||||
|
||||
[grafana-apiserver]
|
||||
; use unified storage for k8s apiserver
|
||||
storage_type = unified
|
||||
|
||||
# Dualwriter modes
|
||||
# 0: disabled (default mode)
|
||||
# 1: read from legacy, write to legacy, write to unified best-effort
|
||||
# 2: read from legacy, write to both
|
||||
# 3: read from unified, write to both
|
||||
# 4: read from unified, write to unified
|
||||
# 5: read from unified, write to unified, ignore background sync state
|
||||
[unified_storage.correlations.correlation.grafana.app]
|
||||
dualWriterMode = 5
|
||||
|
||||
Reference in New Issue
Block a user