Add new validations to manage object_type and metric_type fields - #527
Conversation
🌐 Coverage report
|
|
test integrations |
|
Created or updated PR in integrations repostiory to test this vesrion. Check elastic/integrations#6948 |
|
Latest run with integrations, the following packages have failed their check:
These are the errors for each packages:
|
💚 Build Succeeded
Historycc @mrodm |
|
test integrations |
|
Created or updated PR in integrations repostiory to test this vesrion. Check elastic/integrations#6948 |
|
Adding the JSON Patches to remove these validation in previous versions , packages failing running "test integrations" are not due to https://fleet-ci.elastic.co/blue/organizations/jenkins/Ingest-manager%2Fintegrations/detail/PR-6948/3/ |
|
Hey @mrodm when is it planned to get this changes available in elastic-package? |
We will prepare releases of package-spec and elastic-package today or tomorrow. |
What does this PR do?
This PR adds new validations to include the cases where
object_typeand/ormetric_typeare set in field definitions.object_type(new):typeisobject.metric_typeand anobject_typeaggregate_metric_doublenot allowed.object_typejust could have a different value of possible values:metric_typebut it does not define anobject_typetypejust could have these allowed values:This PR allows field definitions like this:
Previously, it was failing with this error:
Why is it important?
This new validation will check that the types of the fields will be the right ones when
metric_typeis set for a field (gauge or counter). Not all types are valid when this is enabled. Based on this docChecklist
test/packagesthat prove my change is effective.spec/changelog.yml.Related issues