You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The custom pricing data format defined for PRICING_CONFIGMAP_NAME is incorrectly provided in the configmap template. As debugging of the source code shows, it only reads that data properly if defined directly, like this:
Note that the case for what I was testing these data formats, is merging config overrides from a config map defined in PRICING_CONFIGMAP_NAME. That only worked for the direct data format given above, even without extra volumes mounts that the helm chart normally creates, when .Values.opencost.customPricing.enabled=true. Perhaps I am confusing that config option to my special case?
The text was updated successfully, but these errors were encountered:
The custom pricing data format defined for
PRICING_CONFIGMAP_NAME
is incorrectly provided in the configmap template. As debugging of the source code shows, it only reads that data properly if defined directly, like this:See aws example for more possible data overrides.
Note that the case for what I was testing these data formats, is merging config overrides from a config map defined in
PRICING_CONFIGMAP_NAME
. That only worked for the direct data format given above, even without extra volumes mounts that the helm chart normally creates, when.Values.opencost.customPricing.enabled=true
. Perhaps I am confusing that config option to my special case?The text was updated successfully, but these errors were encountered: