Consolidate flow json spec

[jotak]

Description

Consolidate json spec following netobserv/network-observability-console-plugin#383

Dependencies

n/a

Checklist

If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

• Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
• Does this PR require product documentation?
  • If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.
• Does this PR require a product release notes entry?
  • If so, fill in "Release Note Text" in the JIRA.
• Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.
  • If so, make sure it is described in the JIRA ticket.
• QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: +0.08% 🎉

Comparison is base (0ffa93c) 55.32% compared to head (f6034a7) 55.41%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #417      +/-   ##
==========================================
+ Coverage   55.32%   55.41%   +0.08%     
==========================================
  Files          46       46              
  Lines        5995     5995              
==========================================
+ Hits         3317     3322       +5     
+ Misses       2443     2438       -5     
  Partials      235      235              

Flag	Coverage Δ
unittests	55.41% <ø> (+0.08%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[skrthomas]

/lgtm

[skrthomas]

@jotak everything looks OK except a couple of minor inconsistencies that I'd like to keep the same in my file:

• for line 3 & 4: I have this in my file and I would like to keep it that way:
  [id="network-observability-flows-format_{context}"]
  = Network Flows format reference

• For line 10, I have this in my file, and I think it was peer reviewed to be like this, maybe we didn't synch it:
  If you are reading this specification as a reference for the Kafka export feature, you must treat all Labels and Fields as regular fields and ignore any distinctions between them that are specific to Loki.

[jotak]

sure, this is in the header file, I'll update it

[jotak]

done: 8760c99

[jotak]

@skrthomas I fixed the InterfaceDirection xref issue that makes your PR fails https://app.travis-ci.com/github/openshift/openshift-docs/jobs/609884831

[jotak]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jotak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jotak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment