deprecate content_library_item_info due to module generation issues

[mikemorency]

SUMMARY

Fixes issue
#540

Deprecate module content_library_item_info in favor of vmware.vmware.content_library_item_info. The module in this collection was not generated correctly, leading to it failing in some use cases. We cannot easily fix this since the issue is in the openapi spec provided by vmware.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

content_library_item_info

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/ca2f39b34c8441cbb9c3ac54b75e557a

✔️ ansible-test-cloud-integration-vmware-rest SUCCESS in 13m 19s
✔️ build-ansible-collection SUCCESS in 7m 31s
✔️ ansible-galaxy-importer SUCCESS in 3m 51s

[billy-stellar]

@mikemorency does this mean vmware.vmware will soon have a .content_library_item_info module? I don't see that documented today, nor in the source code.

[mikemorency]

Hi @billy-stellar ,

Yes, we will be adding a content_library_item_info module with the next minor release. The PR to add the module is open in the vmware.vmware repo.
Both vmware.vmware and vmware.vmware_rest have minor releases planned in the next ~2 weeks

[mariolenz]

@mikemorency Some of the tests fail. I think I had a similar problem in community.vmware and solved it like this:

https://github.com/ansible-collections/community.vmware/blob/394a5a6bc05288af8054e8d1e20cba94a2957b7d/.github/workflows/extra-docs-linting.yml#L34-L37

I'm not sure if you would also have to install vmware.vmware somewhere explicitly, but I think you should wait until the module really is part of vmware.vmware to make the CI happy.

Both vmware.vmware and vmware.vmware_rest have minor releases planned in the next ~2 weeks

There will be new releases of the Ansible Community Package December 3rd, and the next one will be end of January. It would be great if you could do those releases in time so we can include them! Of course, this will only work if we're talking about minor releases here ;-)

BTW those will be the last 9.x and 10.x releases. From then on, it's ansible 11 or nothing.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.05%. Comparing base (7cc48d2) to head (afcf3c6).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #551   +/-   ##
=======================================
  Coverage   37.05%   37.05%           
=======================================
  Files         145      145           
  Lines       11395    11395           
  Branches     2261     2261           
=======================================
  Hits         4222     4222           
  Misses       7173     7173           

Flag	Coverage Δ
sanity	37.05% <ø> (ø)

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

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

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/7749d840a4c14418afa9d40e1e46c626

✔️ ansible-test-cloud-integration-vmware-rest SUCCESS in 15m 09s
✔️ build-ansible-collection SUCCESS in 7m 40s
✔️ ansible-galaxy-importer SUCCESS in 3m 06s

[mariolenz]

LGTM

Thanks @mikemorency!

[mariolenz]

LGTM

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).
https://ansible.softwarefactory-project.io/zuul/buildset/b03722018d7445fb90f941b7cd48db83

✔️ ansible-test-cloud-integration-vmware-rest SUCCESS in 14m 41s
✔️ build-ansible-collection SUCCESS in 7m 22s
✔️ ansible-galaxy-importer SUCCESS in 6m 37s

[softwarefactory-project-zuul]

Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry.

[mariolenz]

Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry.

@mikemorency I think mergeitdoesn't work if there are any changes to the workflows. Let's just merge it the hard way and test afterwards.

[mariolenz]

It looks like the integration tests still succeed: #553

So let's say it's OK :-)