Currently we find protocol and relevant field in order to set that parameter. We will extend Rest.Py protocol/template so that actual protocol and field information is made available to user as class properties.
to user as class properties.
For example:
# Current way of scripting :
tr1 = traffic.TrafficItem.add(Name='RAW TCP', BiDirectional=False, TrafficType='raw',TrafficItemType='l2L3')
configElement = tr1.ConfigElement.find()[0]
ethernetStackObj = configElement.Stack.find(DisplayName='Ethernet II')
ethernetSrcField = ethernetStackObj.Field.find(DisplayName='Source MAC Address')
ethernetSrcField.SingleValue = '00:11:00:00:22:00'
ipv4ProtocolTemplate = traffic.ProtocolTemplate.find(DisplayName='IPv4')
Currently we find protocol and relevant field in order to set that parameter. We will extend Rest.Py protocol/template so that actual protocol and field information is made available to user as class properties. to user as class properties.
For example: