A record implementation for next available ip #232
Chaithra001Annotations
7 errors and 2 warnings
|
Test (macOS-latest, 1.21):
infoblox/resource_infoblox_a_record.go#L161
objMgr.AllocateNextAvailableIp undefined (type ibclient.IBObjectManager has no field or method AllocateNextAvailableIp)
|
|
Test (macOS-latest, 1.21)
Process completed with exit code 1.
|
|
Test (windows-latest, 1.21)
The job was canceled because "macOS-latest_1_21" failed.
|
|
Test (windows-latest, 1.21)
The operation was canceled.
|
|
Test (ubuntu-latest, 1.21)
The job was canceled because "macOS-latest_1_21" failed.
|
|
Test (ubuntu-latest, 1.21):
infoblox/resource_infoblox_a_record.go#L161
objMgr.AllocateNextAvailableIp undefined (type ibclient.IBObjectManager has no field or method AllocateNextAvailableIp)
|
|
Test (ubuntu-latest, 1.21)
The operation was canceled.
|
|
Test (macOS-latest, 1.21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test (macOS-latest, 1.21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1, actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|