Closed jmeldrum76 closed 1 year ago
Thanks for the detailed writeup @jmeldrum76. This is due to the custom field lookup for attributes not differentiating between certs and devices.
'Environment' is an attribute of 'Ssh Device Base' which 'Device' inherits. When listing all attributes of a device, it will come up to Environment and find a matching custom field and assume that's it which is incorrect. You can rename the custom field and it will work, but I'll look to enhance Get-TppAttribute
to lookup custom fields by the classes they pertain to as well as name.
I am not so sure that is the case. In the screenshot below, you can see my my custom field guid that applies only to certificates. somehow my screenshot is not in the original bug:
@jmeldrum76 you can also use the -NoLookup parameter which will bypass custom field lookups.
That does not solve the problem.
The -NoLookup parameter works for now.
Environment
Steps to reproduce
Its pretty easy:
Expected behavior
I should not get an Exception.
Actual behavior
I am getting an exception on this custom field that is not even present on the device object:
Here is the custom Field configuration:
![image](https://github.com/Venafi/VenafiPS/assets/21229220/c873793d-31e4-4110-8274-a80a1dd56569)
No Custom Field Present:![image](https://github.com/Venafi/VenafiPS/assets/21229220/b4974467-c3fb-4c03-9a95-f24204ce266e)
Full Script