taste-tester
Software to manage a chef-zero instance and use it to test changes on production servers.
by facebookRuby
Commit activity
Last 12 weeks · 7 commits
Community health
4 of 6 standards met
75
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · 2 in progress · Last activity 4w ago
See all on GitHub →
This was a fun one. Chef, when spinning up chef-zero, expects databags to be in 'data_bags', but the default for tt is 'databags', so after testing stuff, it'll then break production when there's no databags. Signed-off-by: Phil Dibowitz
Basically a re-do of #158. This got rolled back because @babar wrote 3 different PRs and one of them was bad. This one wasn't. Technically it wasn't good either, as it only did , not really , or . This re-do fixes this. Still the same features: Can parametrize the number of threads in the config, or on the command line, default to the number of cores Reports hosts depending whether they failed ssh or something else Doesn't have any extra dependency, as the thread pool is done in a very simple way Test Plan: Ran it on my machine. Tried and , both worked. Signed-off-by: Olivier Raginel
Recent fixes
Sometimes we have servers in a firewalled off part of the network and we need to test some chef changes during server provisioning. The test config for the chef client is live and it's awaiting just a reverse tunnel to appear to start the chef run. Due to this I would love a wrapper to start the tunnel(s) rather than manual and manually looking at what port the chef instance is running on.
Two parts: 1. Demonstrate the bug in a unit test 2. Fix the bug
Summary Removes an invalid keyword from the PowerShell script generated by in . The Bug The method generates a PowerShell heredoc for creating SSH tunnels on Windows targets. However, the script incorrectly includes a keyword at the end of the loop: Why This Is Wrong is bash/shell syntax used to close , , and loops PowerShell uses braces ** to delimit code blocks, not keywords A PowerShell loop is simply - no closing keyword needed The line causes a syntax error when Windows attempts to run the tunnel script Impact This bug prevents SSH tunnel creation on Windows targets. When taste-tester attempts to set up a tunnel to a Windows host, PowerShell will reject the script with a syntax error, causing the tunnel setup to fail. Fix Simply remove the stray line. The loop is already properly closed by its closing brace .
Structured data for AI agents
Repository: facebook/taste-tester. Description: Software to manage a chef-zero instance and use it to test changes on production servers. Stars: 147, Forks: 68. Primary language: Ruby. Languages: Ruby (93.8%), Shell (4.4%), PowerShell (1.7%). License: Apache-2.0. Open PRs: 2, open issues: 12. Last activity: 4w ago. Community health: 75%. Top contributors: jaymzh, odcinek, emroch, dafyddcrosby, davide125, NaomiReeves, malmond77, joshuamiller01, nishchintraina, bwann and others.