Repository navigation
Add --restart-container option to devspace sync command #2348
Description
Activity
Hey @petr-buchin! Thanks for creating this issue! I'm not sure if we should add this, since
devspace syncis just meant to sync files into a container, but the--restart-containeroption would lead to replacing the container and injecting the restart helper. This is wanted in the regular dev workflow, but I'm not sure if we should add this for the sync command only as we would also need to add the other options for replacing a container or expect the restart helper to be injected already, which could cause confusion.Thanks again for the suggestion, @petr-buchin .
As Fabian mentioned, we're having some concerns related to the integration of the suggested feature in our overall product concept.I have converted this issue to a discussion so we could address the topic further, if you'd like to.
We would be happy to provide you with more details there!- locked and limited conversation to collaborators
on Oct 21, 2022
Is your feature request related to a problem?
No
Which solution do you suggest?
It would be great to have ability to specify
--restart-containeroption indevspace synccommand, which would add functionality, already available viarestartContaineroption indevspace.yamlconfig.Which alternative solutions exist?
Alternative would be to use
devspace devpipelineAdditional context
I need to run file sync separate from dev pipeline. DevSpace is a great tool, and it would be even better, if standalone
dev synccommand had the same functionality assyncsection indevpipeline./kind feature