Skip to content
This repository has been archived by the owner on May 25, 2022. It is now read-only.

Remove vagrant-triggers plugin #125

Closed
2 tasks done
stevenrombauts opened this issue May 14, 2018 · 0 comments · Fixed by #127
Closed
2 tasks done

Remove vagrant-triggers plugin #125

stevenrombauts opened this issue May 14, 2018 · 0 comments · Fixed by #127
Milestone

Comments

@stevenrombauts
Copy link
Member

stevenrombauts commented May 14, 2018

Since Vagrant 2.1 support for triggers has been added to the core Vagrant implementation. See: https://www.vagrantup.com/docs/triggers/

If you run the box now on 2.1.x, you'll get this warning:

WARNING: Vagrant has detected the `vagrant-triggers` plugin. This plugin conflicts
with the internal triggers implementation. Please uninstall the `vagrant-triggers`
plugin and run the command again if you wish to use the core trigger feature. To
uninstall the plugin, run the command shown below:

  vagrant plugin uninstall vagrant-triggers

Note that the community plugin `vagrant-triggers` and the core trigger feature
in Vagrant do not have compatible syntax.

To disable this warning, set the environment variable `VAGRANT_USE_VAGRANT_TRIGGERS`.

The built-in triggers mechanism is unfortunately not suited for our backup and restore workflow. Because it's absolutely vital that we ask users if they want to create a backup yes or no, we need to drop this feature entirely. Running inline ruby code is not possible with this new triggers method.

Todo's:

  • Remove the triggers and the plugin requirement
  • Update the FAQ to explain how to manually backup and restore.
@stevenrombauts stevenrombauts added this to the 1.5 milestone May 14, 2018
stevenrombauts pushed a commit that referenced this issue Jun 18, 2018
stevenrombauts pushed a commit that referenced this issue Jun 18, 2018
@stevenrombauts stevenrombauts changed the title Refactor vagrant-triggers plugin Remove vagrant-triggers plugin Jun 19, 2018
@stevenrombauts stevenrombauts modified the milestones: 1.5, 1.6, v1.5.1 Oct 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant