Did Pyvmomi's license manager not provide the expiration time for reading certificates
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Connect to the vCenter server through pyvmomi, obtain the license management object of content.licenseManager, read licenses, and find that there is no license expiration time
Reproduction steps
...
Expected behavior
- I hope that when I can directly read licenses, I can obtain the expiration time of the license. Additionally, when the License Assignment Manager is updated simultaneously, QueryAssigned Licenses can retrieve the expiration time of the object's license based on its ID
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing content.licenseManager and the license-reading operations in the pyvmomi bindings, then compare their exposed fields with the vSphere API behavior. Check how License Assignment Manager and QueryAssigned Licenses are represented. Done means the relevant license queries expose expiration time where the API provides it, with coverage for both license reads and assigned-license queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100