SaaShup/netbox-docker-plugin

:sparkles: add "not_sync" flag on container

Open

#131 opened on May 21, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (12 forks)auto 404
V4enhancementgood first issuehelp wanted

Repository metrics

Stars
 (78 stars)
PR merge metrics
 (PR metrics pending)

Description

Netbox version Plugin Version Agent version Docker API Version
3.7.* 1.11.0 * *

Actual Behavior

When I reconfigure a container (changing labels, mounts, ports...) the changes will not be applied until I recreate the container. If I make a change it is highly possible I forgot to recreate or want to postpone the recreation but nobody would know

Desired Behavior

I believe we should flag a container as soon as a change has been applied and the recreate has not been triggered. This way I would know that the actual configuration of my container in the plugin and the actual docker being run is different.

As soon as the recreate is triggered the flag is removed.

Contributor guide

Research direction
Add a boolean field 'needs recreate' to the container model. Update it when container configuration changes via signals or middleware. Expose it in the UI or API as a flag. Clear it when the user triggers a recreate action.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DockerNetboxPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70