vmware / vmware/pyvmomi

Getting Extra fields in Events of inventory, task and events

Open
#644 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
2.3k
Forks
763
PR merge metrics
No merged PRs in 30d

Description

Hello,

I have noticed some extra fields in events of inventory, task and events. These fields are coming in each events.
Here are the fields:
dynamicProperty, dynamicType

Also in some events we have noticed "missingSet" field.
What is significance of these fields? Currently i have never seen any value in these fields. When we can get values in these fields?

Example Event:

{	[-]	
  	 changeSet:	{	[+]	
  	}	
  	 collectionVersion:	 2	
  	 dynamicProperty:	[	[-]	
  	]	
  	 dynamicType:	 None	
  	 missingSet:	[	[-]	
  	]	
  	 moid:	 domain-c26	
  	 rootFolder:	{	[+]	
  	}	
  	 type:	 ClusterComputeResource	
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names inventory, task, and event objects in the pyvmomi vSphere API, but no file, test, or entry point is provided. Start by locating the definitions and documentation for dynamicProperty, dynamicType, and missingSet, then verify when these fields can contain values. Done means documenting their significance and conditions of use.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.