mihaibalint/dfsync

Intelligent remote directories and files sync

dfsync's Issues

Getting `container isn't ready: Unknown` error

When trying to dfsync a container that for some reason has crashed (e.g. previously synced changes contained some bug), I get this error:

<path-to-file> will not sync in <container-name>, container isn't ready: Unknown

As a result, I can't sync files any more (unless I press Ctrl-C or X and let dfsync restore the original container).

Note: This issue was created prior to the release of 0.4.6.

Testing with multiple python version

It's likely that developers will want to use dfsync in various environments with various python versions, it would be great if we could use something like tox to at least run the test suite with the most popular versions of python (like those shipped by OS distributions)

Crash when saving files from pycharm even though .idea gitignored

Deal with "Conflict" responses from kubernetes

Sometimes multiple processes will try and modify pods resulting in a "Conflict" response from the kubernetes API.

Usually the fix for this is to retry the update. Right now, a traceback is generated and dfsync exits.

No warning when trying to sync file without permissions

If no .venv in project dir then the .venv will be remove on the destination

Integrate with pyproject.toml

it turns out that the length and number of command line arguments keeps growing, it would be more user friendly to move some of that into the tools section of pyproject.toml

Incorrect pods selection for sync when multiple pods have a name starting with the same string

We have two projects that result in images on harbor with the following names:
/central-hub
/central-hubspot-enricher

Now, if we do a dfsync to sync central-hub, we will actually replace the code on both projects. It seems like dfsync checks only that the image name on Kubernetes starts with the specified image name not that it is exactly what we specified as first parameter.

Add usage instructions

Awesome work, thanks a lot!

Can we get info on stuff such as:

• installation
• cmdline usage examples
• cmdline reference
• tool configuration
  ?

Thanks a lot for your hard work, this is very helpful!

[Feature Request] Support multiple kubernetes clusters

It would be useful to be able to run two dfsyncs in two different terminals that are syncing two different pods in two different kubernetes clusters on two different projects.
Thanks.

Add a basic readme file

Information such as purpose and installation instructions is welcome

Quality of life improvements

• Add command to print tool version + the latest available version
• Generate a warning message if using an outdated version of dfsync
• Enable running from within the project folder

Importing with dfsync import-kube-host --kube-host=192.168.0.2:6443 does not work

An error is generated

Automated unit testing

There are many cases to cover when syncing file changes to a destination so a minimal test suite would be a good thing

Feature roadmap

• Run kubectl exec in the same shell as dfsync to avoid having to switch between terminals
• Detect and start the app process automatically after having synced the code in the container
• Implement key-bindings (similar to screen) for useful commands: force full sync, restart the app, etc

Enforce permissions for `~/.kube/config`

~/.kube/config is a sensitive file, it's permissions should be at least equivalent to "chmod go-rwx"

Without this, kubectl will also complain when trying tu use that file

I am getting python threading error related to FileChangedEventHandler

Watching dir(s): '.'; press [Ctrl-C] to exit

Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/home/.../.venv/lib/python3.9/site-packages/watchdog/observers/api.py", line 199, in run
self.dispatch_events(self.event_queue, self.timeout)
File "/home/.../.venv/lib/python3.9/site-packages/watchdog/observers/api.py", line 372, in dispatch_events
handler.dispatch(event)
File "/home/.../.venv/lib/python3.9/site-packages/watchdog/events.py", line 282, in dispatch
self.event_dispatch_mapevent.event_type
AttributeError: 'FileChangedEventHandler' object has no attribute 'event_dispatch_map'

Add ability to sync untracked git files

I was working on a new feature with uncommitted changes and found out only after a while that a new untracked file was not syncing. By looking at dfsync sync --help it doesn't seem to be possible to sync untracked files.