Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to Vagrant SyncedFolders #295

Merged
merged 1 commit into from
Nov 14, 2016

Conversation

Sharpie
Copy link
Contributor

@Sharpie Sharpie commented Jul 30, 2016

Vagrant 1.5 introduced a standard SyncedFolders middleware which can be re-used
by providers to implement things such as rsync support. This patch uses Vagrant
SyncedFolders as the default sync implementation instead of the legacy
SyncFolder implementation inherited from the Rackspace project.

The legacy implementation is retained for backwards compatibility and will be
used if any of the following provider options is set:

  • rsync_includes
  • rsync_ignore_files
  • sync_method

A deprecation warning will be printed.

@Sharpie Sharpie force-pushed the use-standard-synced-folders branch from 0b04b15 to e01ef2e Compare July 30, 2016 19:03
@coveralls
Copy link

coveralls commented Jul 30, 2016

Coverage Status

Coverage decreased (-0.2%) to 91.396% when pulling e01ef2e on Sharpie:use-standard-synced-folders into eb06809 on ggiamarchi:master.

Vagrant 1.5 introduced a standard SyncedFolders middleware which can be re-used
by providers to implement things such as rsync support. This patch uses Vagrant
SyncedFolders as the default sync implementation instead of the legacy
SyncFolder implementation inherited from the Rackspace project.

The legacy implementation is retained for backwards compatibility and will be
used if any of the following provider options is set:

  - rsync_includes
  - rsync_ignore_files
  - sync_method

A deprecation warning will be printed.
@Sharpie Sharpie force-pushed the use-standard-synced-folders branch from e01ef2e to 2fb940d Compare July 31, 2016 18:13
@coveralls
Copy link

coveralls commented Jul 31, 2016

Coverage Status

Coverage decreased (-0.2%) to 91.396% when pulling 2fb940d on Sharpie:use-standard-synced-folders into eb06809 on ggiamarchi:master.

@Sharpie
Copy link
Contributor Author

Sharpie commented Sep 10, 2016

@ggiamarchi Thoughts on this change? The built-in synced folder implementation has many more features, and supports nice things like auto-installation of rsync. It also allows multiple synced folders to be set up, allows a single set of exclusions to be used across multiple providers, and allows for alternate sync methods such as NFS.

@ggiamarchi
Copy link
Owner

@Sharpie No worries, I definitely agree moving to the built-in synced folder implementation is a thing to do ! Furthermore, there's a few issues and PR opened regarding synced folders on the OpenStack provider and i guess moving to the built-in implementation will resolve most of them. I'll try to take time soon to test and review.

By the way, if someone else wants to help testing and feedback about about this one it would be really valuable.

@craigtracey, @Aaronboyle, @brijs you could be interested in this one.

@ggiamarchi ggiamarchi merged commit 4e2d701 into ggiamarchi:master Nov 14, 2016
@ggiamarchi
Copy link
Owner

@Sharpie Thanks for this great contribution and sorry for the long time to merge !

@Sharpie
Copy link
Contributor Author

Sharpie commented Nov 16, 2016

No worries! The FOSS projects I manage tend to have similar review lengths :)

Thanks for the merge!

@Sharpie Sharpie deleted the use-standard-synced-folders branch November 16, 2016 16:48
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this pull request Dec 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants