Actions243
- Cable Actions
- Cable Termination Actions
- Connected Device Actions
- Console Port Actions
- Console Port Template Actions
- Console Server Port Actions
- Console Server Port Template Actions
- Device Actions
- Device Bay Actions
- Device Bay Template Actions
- Device Role Actions
- Device Type Actions
- Front Port Actions
- Front Port Template Actions
- Interface Actions
- Interface Template Actions
- Inventory Item Actions
- Inventory Item Role Actions
- Inventory Item Template Actions
- Location Actions
- MAC Address Actions
- Manufacturer Actions
- Module Actions
- Module Bay Actions
- Module Bay Template Actions
- Module Type Actions
- Module Type Profile Actions
- Platform Actions
- Power Feed Actions
- Power Outlet Actions
- Power Outlet Template Actions
- Power Panel Actions
- Power Port Actions
- Power Port Template Actions
- Rack Actions
- Rack Reservation Actions
- Rack Role Actions
- Rack Type Actions
- Rear Port Actions
- Rear Port Template Actions
- Region Actions
- Site Actions
- Site Group Actions
- Virtual Chassis Actions
- Virtual Device Context Actions
- Virtual Link Actions
Module Bay → Delete
AI-generatedOverview
This node interacts with the NetBox API to delete a specific Module Bay resource within the DCIM domain. It is useful in scenarios where you need to programmatically remove module bay records from your NetBox instance, such as during automated infrastructure cleanup or management workflows.
Use Case Examples
- Deleting a module bay by specifying its ID to keep the NetBox inventory up to date.
- Automating the removal of module bays as part of a device decommissioning process.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to interact with, here it is set to 'dcim' for data center infrastructure management. |
| Module Bay ID | The unique identifier of the module bay to be deleted. |
Output
JSON
json- The JSON response from the NetBox API after attempting to delete the module bay, typically indicating success or failure.
Dependencies
- Requires an API key credential for authenticating with the NetBox API.
Troubleshooting
- Common issues include providing an invalid or non-existent Module Bay ID, which will result in an error from the API.
- Authentication failures due to incorrect or missing API credentials.
- Network connectivity issues preventing access to the NetBox API endpoint.