Wojciech Wypior
Wojciech Wypior
##### SUMMARY The conditonal class in parsing.py seems to require using `result` keyword when implemeting wait_for. We have implemented wait_for in our collection, and we use Conditional class from `plugins/module_utils/network/common/parsing.py`...
Currently most of our sanity checks for parameters rely on **kwargs passed to update(), those sanity checks do not work when the user adds object attributes directly: ```` r1.description ==...
currently when you specify password attribute and attempt to update() existing user, REST returns error: \\"password\\" may not be specified with \\"encrypted-password\\"","errorStack":[]}' We need some logic to prevent this.
We would need some tests ISOs to be present in our harness to be able to test image/hotfix management. i.e deletion, upload, installation For now those endpoints will remain without...
opening this issue to create messaging/logging system for SDK,
/mgmt/tm/shared/licensing/activation endpoint in REST supports POST, currently we do not allow POST, since this is Unnamed Resource: https://github.com/F5Networks/f5-common-python/blob/acb2efb4e902afaf12b56e1794efe1cb17211493/f5/bigip/tm/shared/licensing.py#L59 I will fix this immediate problem but we need to start looking...
Apart from /stats we have /sys/hostInfo and /sys/memory endpoints which present data in a specific format. While we have a utility that will format that data if the user chooses...
As per comment in PR #1040, I would like us to discuss the established patterns for testing in this library, these will include: - What we test in unit and...