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

converge binaries used in integration tests and examples #356

Open
ryane opened this issue Oct 7, 2016 · 1 comment
Open

converge binaries used in integration tests and examples #356

ryane opened this issue Oct 7, 2016 · 1 comment

Comments

@ryane
Copy link
Contributor

ryane commented Oct 7, 2016

Currently, any integration test (forthcoming in #355) or examples (elk, swarm)
that use the Vagrant or Terraform provisioners are tied to the latest official
release of converge. This means that they will break if they are updated to take
advantage of new unreleased converge features. The only workaround at this point
(afaik) is to upload a locally built converge binary to a public url somewhere
and then build a custom version of the provisioner that points to that location.

It would be nice if we had a way for users and developers to run the tests and
examples using a locally built converge.

Potential solutions:

  • update Terraform and Vagrant provisioners to allow sourcing the converge
    binary from a location on the local filesystem
  • publish nightly releases to a public location and support configuring the
    provisioners to point there
  • Other ideas?
@ryane
Copy link
Contributor Author

ryane commented Oct 7, 2016

note this affects, at minimum, #346, #355, and #334 (just the elk example part of it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant