:sparkles: Restrict container actions

[linkdd]

Decision Record

Closes #119. Closes https://github.com/SaaShup/netbox-docker-agent/issues/55

Actions on a container should not be possible based on its state:

	created	restarting	running	paused	exited	dead	none
Create	❌	❌	❌	❌	❌	❌	✅
Start	✅	❌	❌	❌	✅	✅	❌
Stop	❌	❌	✅	❌	❌	❌	❌
Restart	❌	❌	✅	❌	❌	❌	❌
Recreate	✅	❌	✅	❌	✅	✅	❌
Delete	✅	❌	❌	✅	✅	✅	❌
---	---	---	---	---	---	---	---
None	✅	✅	✅	✅	✅	✅	✅

(edited by @lvenier)

NB: If the state is none (therefore, the agent failed to communicate the container's real state), then we prevent any action until it is resolved, as we cannot guarantee anything, except when:

• a container is created with operation=create and state=none, which must be valid
• the agent updates a container's state, it sets operation=none, which must always be valid

It does not seem possible to add a disabled state to the delete/bulk-delete buttons in Netbox. Therefore, the pre_delete model signal should be intercepted to apply the constraint there.

Changes

• [x] :lipstick: Add disabled state on container's extra control buttons
• [x] :sparkles: Prevent container model deletion if state is running / restarting
• [x] :sparkles: Prevent container model save if state and operation do not pass restrictions check
• [x] :white_check_mark: Add test suite to validate container restricted actions

[github-actions[bot]]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
2152	2118	98%	90%	✅

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 235665c by action🐍

[lvenier]

	created	restarting	running	paused	exited	dead	none
Create	❌	❌	❌	❌	❌	❌	❌
Start	✅	❌	❌	❌	✅	✅	❌
Stop	❌	❌	✅	❌	❌	❌	❌
Restart	❌	❌	✅	❌	❌	❌	❌
Recreate	✅	❌	✅	❌	✅	✅	❌
Delete	✅	❌	❌	✅	✅	✅	❌

[lvenier]

I see an improvement for the next PR : if container operation == "none" then no operation allowed on container