WHY
Please see case: https://github.com/3scale/3scale-operator/issues/597

WHAT
See details in Case (following is copied from https://github.com/3scale/3scale-operator/issues/597)

• Metrics and mapping rules are defined in the backend
• Product simply "consumes" the backend, and define application plans
• Issue : the Product CR fails to be processed with the following message :

'[spec.applicationPlans[free].limits[1].metricMethodRef: Invalid value: "callsToPremium": limit does not have valid local metric or method reference., spec.applicationPlans[payAsYouGo].pricingRules[0].metricMethodRef: Invalid value: "callsToPremium": Pricing rule does not have valid local metric or method reference., spec.applicationPlans[payAsYouGo].pricingRules[1].metricMethodRef: Invalid value: "callsToPremium": Pricing rule does not have valid local metric or method reference., spec.applicationPlans[payAsYouGo].pricingRules[2].metricMethodRef: Invalid value: "callsToV2": Pricing rule does not have valid local metric or method reference.]'

See All notes of Eguzki in the Case:

• missing the reference in Product CR to the backend in the limit section of Product CR
• references of metrics from the pricing rules are also missing backend reference.

HOW

• Use Backend CR as in Case
• Use Fixed Product CR, see notes of Eguzki (and in What section)

Example for "Limit" issue fix in CR is below. Example for Reference of metrics fix in CR - please do it as part of Test.

       - period: month
          value: 0
          metricMethodRef:
            systemName: callsToPremium
            backend: micro-api-backend    <- missing

TEST
Check scenarion described in Case. See notes in HOW section, check that error is not present
If error still exist - continue Investigation / fix

DONE
Scenation described in Case passed without errors