We could not migrate our input packages like sql_input, statsd_input, etc. to use package-spec v3+ and as a consquence we are not able to use the new additions and one of the them is fips_compatible flag.
We would like to disable SQL input for ECH FedRAMP; however, since it is still utilizing package-spec v2, we are unable to utilize the flag.
Here's the reason why we couldn't migrate the input packages to v3: elastic/integrations#8291 (comment) (reason: object_type is required for object type)
object_type is required for metrics.* (see here) and metrics.* mapping is added to the input only for sample event generation purpose. More details Here's the reason why we couldn't migrate the input packages to v3: elastic/integrations#8291 (comment).
We could not migrate our input packages like sql_input, statsd_input, etc. to use package-spec v3+ and as a consquence we are not able to use the new additions and one of the them is
fips_compatibleflag.We would like to disable SQL input for ECH FedRAMP; however, since it is still utilizing package-spec v2, we are unable to utilize the flag.
Here's the reason why we couldn't migrate the input packages to v3: elastic/integrations#8291 (comment) (reason:
object_typeis required forobjecttype)object_typeis required formetrics.*(see here) andmetrics.*mapping is added to the input only for sample event generation purpose. More details Here's the reason why we couldn't migrate the input packages to v3: elastic/integrations#8291 (comment).