Request: Add Optional Parameter to Skip Volume/Network on Destroy
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, docker-compose, go
- Domain
- devops, infrastructure
Research direction
No files, tests, or entry points are named. Start by tracing how dockform reads context volume and network declarations and how destroy handles them; define completion as supporting an optional destroy: false setting that preserves the selected volumes and networks while existing declarations retain current behavior.
Written by the indexing model from the issue text.
Description
I generally use contexts.<name>.volumes for filesets and volumes that contain config files and declare volumes in the compose file that contain data files to avoid purging that data when I destroy a stack. I prefer to always delete data volumes manually. It would be nice to be able to also declare those volumes in the dockform.yaml with an additional option to ignore them. While I don't do this at the moment for networks, it seems like this could also apply there as well.
For Example:
contexts:
default:
networks:
network-1:
network-2:
destroy: false
volumes:
config-volume:
data-volume:
destroy: false
- Dominant language
- Go
- Stars
- 248
- Forks
- 6
- Avg merge
- 5h 32m
- Merged PRs (30d)
- 19
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from gcstr/dockform
-
Documentation update Open
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100