1. Remove shell-word escaping from extended test execution code (details)
  2. Customer Diagnostics commands (details)
Commit 03b1fe3697c9526217f4212ad86e712bf57e2350 by Steve Kuznetsov
Remove shell-word escaping from extended test execution code
A valid extended test bucket name should never contain any special shell
characters, so it is unnecessary to attempt to escape them. Similarly,
the only characters inside of a focus string that we are vulnerable to
are double-quotes. Extended test focuses should not contain literal
double quotes, so we should not need to escape anything in those either.
Signed-off-by: Steve Kuznetsov <>
The file was modifiedlib/vagrant-openshift/action/run_origin_tests.rb (diff)
Commit 8412ac92f678868dd25ac7f5ab0c11ea49f55132 by Brenton Leanhardt
Customer Diagnostics commands
The customer diagnostics team is prototyping a test suite written in go
for testing ansible-based tooling.  Right now we're still in the early
stages so a fork of openshift-ansible is being used.  If things go well
by the end of the sprint we expect to merge this to openshift-ansible
and at that time we'd update the urls accordingly.
The goal with these new commands is simply to enable a test and merge
workflow that matches other Origin teams.  The implementation is almost
entirely similar to the other sync and test commands that we have.
The file was addedlib/vagrant-openshift/command/test_customer_diagnostics.rb
The file was modifiedlib/vagrant-openshift/constants.rb (diff)
The file was addedlib/vagrant-openshift/command/repo_sync_customer_diagnostics.rb
The file was modifiedlib/vagrant-openshift/plugin.rb (diff)
The file was addedlib/vagrant-openshift/action/run_customer_diagnostics_tests.rb
The file was modifiedlib/vagrant-openshift/action.rb (diff)