Migrate obs-infraobs-integrations to package-spec v3 #5

[shmsr]

Cherry-picked changes for 2 packages to this branch so that #8171 gets unblocked:

• mongodb
• influxdb

Proposed commit message

Migrate the following package to use package-spec v3:

• mongodb
• influxdb

Here influxdb ci is failing for some unknown reason i.e., it failing with an error where it shouldn't. And mongodb needs to be tested to check if no data loss is there (tsdb).

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-10-23T09:58:59.012+0000

• Duration: 18 min 2 sec

Test stats 🧪

Test	Results
Failed	0
Passed	32
Skipped	0
Total	32

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	92.683% (38/41)	👎 -1.132
Lines	68.217% (88/129)	👎 -14.176
Conditionals	100.0% (0/0)	💚

[tommyers-elastic]

LGTM - only question is about addition of beta release tags to data streams. thanks!

[shmsr]

@tommyers-elastic Do you know someone who can help with the CI issue we're facing with influxdb?

Ref: #8171 (comment)

[shmsr]

#8028 (comment)

We're good with mongodb tsdb testing ^^

[shmsr]

Upgraded the stack version for influxdb to ^8.9.0 to fix the constant CI failures:

Error: error running package system tests: could not complete test run: failed to install package: can't install the package: could not zip-install package; API status code = 500; response body = {"statusCode":500,"error":"Internal Server Error","message":"illegal_argument_exception\n\tRoot causes:\n\t\tillegal_argument_exception: Limit of total dimension fields [21] has been exceeded"}

[shmsr]

@tommyers-elastic Should I merge this PR?

[tommyers-elastic]

i'm happy to upgrade the stack version to make the CI more reliable. @lalit-satapathy how about you?

[lalit-satapathy]

i'm happy to upgrade the stack version to make the CI more reliable. @lalit-satapathy how about you?

@shmsr, Is the new conclusion that the CI is passing in 8.9.* and failing in 8.8.* for dimension_fields override? Our earlier understanding as per this, lead to conclude that, the issue is resolved in 8.8.* onwards.

I am fine, in that is case to upgrade to 8.9. Need to summarise and to see if any changes needed in other packages. Example kafka?

CC: @agithomas

[shmsr]

i'm happy to upgrade the stack version to make the CI more reliable. @lalit-satapathy how about you?

@shmsr, Is the new conclusion that the CI is passing in 8.9.* and failing in 8.8.* for dimension_fields override? Our earlier understanding as per this, lead to conclude that, the issue is resolved in 8.8.* onwards.

I am fine, in that is case to upgrade to 8.9. Need to summarise and to see if any changes needed in other packages. Example kafka?

CC: @agithomas

For some unknown reason it is only happening for influxdb and this is the reason why I pulled out influxdb from #8171 to unblock that PR from merging.

After failing to conclude why the CI failed for influxdb, I tried reproducing this locally, and there too the tests were failing with with 8.8.0 stack. But for 8.9.0 it passed.

[lalit-satapathy]

For some unknown reason it is only happening for influxdb and this is the reason

So long as it consistently passes in 8.9 and fails in 8.8, we can conclude that some external change done in 8.9 stack.

[elasticmachine]

Package influxdb - 0.7.0 containing this change is available at https://epr.elastic.co/search?package=influxdb

[elasticmachine]

Package mongodb - 1.12.0 containing this change is available at https://epr.elastic.co/search?package=mongodb