build(deps): update module github.com/shopify/toxiproxy to v2.5.0
What does this MR do?
Updates toxiproxy to v2.5.0
. We need a manual update instead of !1391 (comment 1514774499) as the package is now go.mod compatible, so it required a few more changes.
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
github.com/Shopify/toxiproxy | require | minor |
v2.1.4+incompatible -> v2.5.0
|
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
Shopify/toxiproxy
v2.5.0
Changes
- Update Release steps. (#369, @neufeldtech)
- Migrate off probot-CLA to new GitHub Action. (#405, @cursedcoder)
- Support go 1.18, 1.19. (#415, @miry)
-
toxiproxy.NewProxy
now acceptsname
,listen addr
andupstream addr
. (#418, @miry) - Replace logrus with zerolog. (#413, @miry)
- Log HTTP requests to API server. (#413, #421, @miry)
- Add TimeoutHandler for the HTTP API server. (#420, @miry)
- Set Write and Read timeouts for HTTP API server connections. (#423, @miry)
- Show unique request id in API HTTP response. (#425, @miry)
- Add method to parse
stream.Direction
from a string. Allow convertingstream.Direction
to string. (#430, @miry) - Add the possibility to write to Output with a deadline. On interrupting Bandwidth toxic, use non-blocking writes. (#436, @miry)
- Update minimum supported Go version 1.17. (#438, @miry)
New Contributors
- @waseem made their first contribution in https://github.com/Shopify/toxiproxy/pull/402
- @cursedcoder made their first contribution in https://github.com/Shopify/toxiproxy/pull/405
Full Changelog: https://github.com/Shopify/toxiproxy/compare/v2.4.0...v2.5.0
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.5.0
Homebrew
brew install shopify/shopify/toxiproxy
v2.4.0
- Verify git tag on release (#347, @miry)
- Fix MacOS 12 tests for go17 with -race flag (#351, @strech)
- Rename
testing/
andbin/
folders (#354, @strech) - Added verbose error on proxy upstream dialing (#355, @f-dg)
- Improve server startup message (#358, @areveny)
- Introduce yaml linter. (#362, @miry)
- Handle slicer toxic with zero
SizeVariation
and fix slicing randomization (#359, @areveny) - Added /metrics endpoint for exposing Prometheus-compatible internal metrics (#366, @neufeldtech)
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.4.0
v2.3.0
- Store all the executable
main
packages incmd
folder. (#335, @miry) - Extract common test helpers to own files. (#336, @miry)
- Client: Allow HTTPS endpoints. (#338, @chen-anders)
- client.Populate assign client to proxy. (#291, @hellodudu)
- fix: The release-test task is always success. add: Allow to run release-test on arm machines. (#340, @miry)
- Upgrade
goreleaser
. Supportarmv7
andarmv6
oses. (#339, @mitchellrj) - Allow to change log level for server. (#346, @miry)
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.3.0
v2.2.0
- Update linux packages to use
/usr/bin
folder as binary destination and change the executable names to exclude ARCH and OS names. New pathes: /usr/bin/toxiproxy-cli /usr/bin/toxiproxy-server (#331, @miry) - A new toxic to simulate TCP RESET (Connection reset by peer) on the connections by closing the stub Input immediately or after a timeout. (#247 and #333, @chaosbox)
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.2.0
v2.1.7
- Set the valid version during the build process.
Verify the correct verion of the built binaries with
make release-dry
(#328, @miry)
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.1.7
v2.1.6
- Use CHANGELOG.md for release description (#306, @miry)
- Dependency updates in #294 introduced a breaking change in CLI argument parsing. Now flags must be specified before arguments. Previously, arguments could be specified prior to flags. Update usage help text and documentation. (#308, @miry)
- Run e2e tests to validate the command line and basic features of server, client and application (#309, @miry)
- Add /v2 suffix to module import path (#311, @dnwe)
- Setup automated checking source code for security vulnerabilities (#312, @miry)
- Setup code linter (#314, @miry)
- Max line length is 100 characters (#316, @miry)
- Linter to check whether HTTP response body is closed successfully (#317, @miry)
- Make sure the function are not big (#318, @miry)
- Extract client flags specs to seprate methods.
Introduce a new way to manage toxics with
ToxicOptions
sturcture (#321, @miry) - Split
Proxy.server
to multiple small (#322, @miry) - Extract initializetion of fake upstream server to test helper (#323, @miry)
- Support a list of well knonwn linters (#326, @miry)
- Extract client flags specs to seprate methods.
Introduce a new way to manage toxics with
-
--host
flag usesTOXIMROXY_URL
if it is set (#319, @maaslalani) - Run benchmarks in CI/CD (#320, @miry)
- Use scratch docker base image instead of alpine (#325, @miry)
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.1.6
v2.1.5
Changelog
- Move to Go Modules from godeps (#253, @epk)
- Update the example in
client/README.md
(#251, @nothinux) - Update TOC in
README.md
(4ca1edd
, @dwradcliffe) - Add an example of
config.json
file toREADME.md
(#260, @JesseEstum) - Add Link to Elixir Client (#287, @Jcambass)
- Add Rust client link (#293, @itarato)
- Renovations: formatting code, update dependicies, make govet/staticcheck pass (#294, @dnwe)
- Remove
openssl
fromdev.yml
to usedev
tool (#298, @pedro-stanaka) - Update
go
versions in development (#299, @miry) - Mention
MacPorts
inREADME.md
(#290, @amake) - Fix some typos in
README.md
andCHANGELOG.md
(#222, @jwilk) - Replace TravisCI with Github Actions to run tests (#303, @miry)
- Build and release binaries with
goreleaser
. Supportarm64
and BSD oses. (#301, @miry) - Automate release with Github actions (#304, @miry)
Commits
eb81bfd
Add Elixir Client to Readme
f1070b0
Add Rust client link.
18165c8
Add example config.json file to README.md
653f495
Automate release with Github actions (#302)
8029ed1
Create releases with goreleaser (#301)
916f03a
Fix typos
d26384f
Fixing dev.yml to allow running dev up
5321df3
Mention MacPorts in readme
8474b0e
Merge branch 'master' into add_toxiproxy_elixir
b0ba1c8
Merge pull request #1 from Shopify/master
07d7b63
Merge pull request #241 from Shopify/v2.1.4
10f0561
Merge pull request #251 from nothinux/master
0ba0d2b
Merge pull request #253 from Shopify/updates
cfe8289
Merge pull request #260 from JesseEstum/example_config
c262ed0
Merge pull request #287 from Jcambass/add_toxiproxy_elixir
115744c
Merge pull request #293 from Shopify/feature/PA-Add-rust-client
335da76
Merge pull request #294 from dnwe/dnwe/renovations
769a33c
Merge pull request #297 from Shopify/update-bundler-2.2.22-1
047ab7f
Merge pull request #298 from Shopify/dev-compat
9134ef6
Move to go modules
758c1e5
Release 2.1.5 (#305)
0653399
Run tests for master and pull requests (#303)
5e860e5
Support solaris platform (#304)
517a128
Update build badge to Travis CI
9e1d709
Update bundler to 2.2.22
82715a0
Upgrade Golang and Ruby versions (#299)
febff58
chore: fix some minor govet/staticheck failures
ad7d9e2
chore: gofmt -s -w
f135051
chore: renovate dependencies
4ca1edd
fix TOC in readme
5bb6b89
update docs
Docker images
docker pull ghcr.io/shopify/toxiproxy:2.1.5
Author checklist
-
Feature flags
-
Added feature flag: -
This feature does not require a feature flag
-
-
I added unit tests or they are not required -
I added documentation (or it's not required) -
I followed code review guidelines -
I followed Go Style guidelines -
For database changes including schema migrations: -
Manually run up and down migrations in a postgres.ai production database clone and post a screenshot of the result here. -
If adding new queries, extract a query plan from postgres.ai and post the link here. If changing existing queries, also extract a query plan for the current version for comparison. -
Do not include code that depends on the schema migrations in the same commit. Split the MR into two or more.
-
-
Ensured this change is safe to deploy to individual stages in the same environment ( cny
->prod
). State-related changes can be troublesome due to having parts of the fleet processing (possibly related) requests in different ways.
Reviewer checklist
-
Ensure the commit and MR tittle are still accurate. -
If the change contains a breaking change, apply the breaking change label. -
If the change is considered high risk, apply the label high-risk-change -
Identify if the change can be rolled back safely. (note: all other reasons for not being able to rollback will be sufficiently captured by major version changes).
If the MR introduces database schema migrations:
-
Ensure the commit and MR tittle start with fix:
,feat:
, orperf:
so that the change appears on the Changelog
If the changes cannot be rolled back follow these steps:
-
If not, apply the label cannot-rollback. -
Add a section to the MR description that includes the following details: -
The reasoning behind why a release containing the presented MR can not be rolled back (e.g. schema migrations or changes to the FS structure) -
Detailed steps to revert/disable a feature introduced by the same change where a migration cannot be rolled back. (note: ideally MRs containing schema migrations should not contain feature changes.) -
Ensure this MR does not add code that depends on these changes that cannot be rolled back.
-