Spinnaker Integration Validation: V1

[yogesh-s-modak]

What does this PR do?

Porting over from Spinnaker Integration PR.

Motivation

Squashing 69 commits into one PR.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.99%. Comparing base (f3e57bd) to head (dbf9cf5).
Report is 55 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
nvidia_nim	?
presto	?
solr	?

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

[neko-dd]

Created DOCS-9633 for docs review

[steveny91]

@yogesh-s-modak Just to confirm again, there's no python code needed for this integration right? It's just logs parsing and dashboard definitions, correct? If so then I think we can remove a lot of files from here. When creating the template for the integration, you can pass in -t logs next time if you want to create a logs only integration. After confirmation, I can help you with what files needs to be removed.

[yogesh-s-modak]

@yogesh-s-modak Just to confirm again, there's no python code needed for this integration right? It's just logs parsing and dashboard definitions, correct? If so then I think we can remove a lot of files from here. When creating the template for the integration, you can pass in -t logs next time if you want to create a logs only integration. After confirmation, I can help you with what files needs to be removed.

@steveny91 We have kept this PR on hold for the moment, because after discussion with Ilya, we came to a conclusion that this connector needs metrics to be included, along with logs. We will need to ascertain what metrics will be included, update the design docs and the PR, and go from there. Due to this, along with log parsing and dashboard definitions, there will be Python code in line with what is required for a metrics connector.

[steveny91]

@yogesh-s-modak No problem! Would you mind converting this PR to a draft and then when it's ready mark it ready for review again?

[yogesh-s-modak]

@yogesh-s-modak No problem! Would you mind converting this PR to a draft and then when it's ready mark it ready for review again?

Done. I'll mark it with the relevant tags as and when we proceed.