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
What
After the recent refactoring where aggregation-method was moved into the parameter-metadata we have two conflicting ways to define the aggregation method - it is still an expected field in the to level aggregation config. We need to remove this field from the top level config to unblock the method definition in the metadata.
Why
We currently have two conflicting places to define aggregation method.
Context
part of parameter metadata upgrade
Currently the aggregation config looks as follows, with method being a required field:
aggregation:
metrics:
"cpu/utilization":
method: avgtype: both
It should be updated to the following:
aggregation:
metrics:
- carbon
- energytype: both
Prerequisites/resources
n/a
SoW (scope of work)
update config as described above
update manifests that use aggregate feature
documentation updated
test cases added if necessary
Acceptance criteria
Given (Setup): The requested changes have been made
What
After the recent refactoring where
aggregation-method
was moved into theparameter-metadata
we have two conflicting ways to define the aggregation method - it is still an expected field in the to level aggregation config. We need to remove this field from the top level config to unblock the method definition in the metadata.Why
We currently have two conflicting places to define aggregation method.
Context
part of parameter metadata upgrade
Currently the aggregation config looks as follows, with
method
being a required field:It should be updated to the following:
Prerequisites/resources
n/a
SoW (scope of work)
Acceptance criteria
Given (Setup): The requested changes have been made
When (Action): i run the following manifest
Then (Assertion): I get the following result
The text was updated successfully, but these errors were encountered: