Skip to content

Commit c490df3

Browse files
author
Ben Blackmore
committed
docs: attack list how-to
1 parent 6507ab1 commit c490df3

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/how-to/write-an-attack-extension.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,4 +41,6 @@ https://github.com/steadybit/action-kit/blob/128d8c05bdadb54e8b001391ead530e22d2
4141

4242
There are no special parameter contracts for attacks. So within this area, you will define them just like any other action. Also, refer to our [parameter types documentation](../parameter-types.md) to learn more about the supported parameter types.
4343

44-
https://github.com/steadybit/action-kit/blob/128d8c05bdadb54e8b001391ead530e22d2d17a3/examples/go-kubectl/handlers.go#L51-L66
44+
https://github.com/steadybit/action-kit/blob/128d8c05bdadb54e8b001391ead530e22d2d17a3/examples/go-kubectl/handlers.go#L51-L66
45+
46+
The last part of the action description is the list of endpoints to call when preparing, starting, checking and stopping the attack. The following sections will explain each endpoint's responsibility in more detail. For now, understand that you can define arbitrary HTTP endpoint paths.

0 commit comments

Comments
 (0)