Update chaos engg docs with recent product changes

[viren-nadkarni]

Caution

Reviewers please do not merge

Background

Following product changes are planned for the LocalStack Chaos Engineering tool suite:

FIS

• The emulation capabilities are being moved to Enterprise tier
• Lower pro tiers will retain the mock capabilities
• LocalStack-specific actions are being deprecated

Outages Extension

• Support is being dropped

Chaos Plugin

• New feature
• Supports everything that outages extension and FIS earlier supported
• Features a powerful configuration language that allows for a finer control over faults and network effects

Changes

• Adds the Chaos Plugin's new internal endpoints
• Tutorial for FIS is removed. Most of the content is migrated to the new Chaos Plugin tutorial
• Route53 Failover tutorial, which earlier used FIS, now makes use of the Chaos Plugin
• A tutorial highlighting the Error Probabilities config options in Community
• Updates the FIS service page to reflect deprecations and other updates
• Add new page for Chaos Plugin in the Chaos Engineering section
• The FIS page in Chaos Engineering section is updated to warn about reprecations
• Outages Extension page in Chaos Engineering section now has the appropriate warning about EOL
• The page documenting the Error Probabilities config options in Community is removed to encourage use of the Chaos Plugin

TODO

• Services / FIS: http://localhost:1313/user-guide/aws/fis/
• Chaos Engg / Chaos plugin: http://localhost:1313/user-guide/chaos-engineering/chaos/
• Chaos Engg / Outages extension: http://localhost:1313/user-guide/chaos-engineering/outages-extension/
  • Sample: https://github.com/localstack-samples/samples-chaos-engineering/tree/updates/extension-outages
• Chaos Engg / FIS: http://localhost:1313/user-guide/chaos-engineering/fault-injection-service/
• Tutorial / Route53 Failover: http://localhost:1313/tutorials/route-53-failover/
  • Sample: Fix samples to reflect product updates localstack-samples/samples-chaos-engineering#2
• Tutorial / Chaos Plugin: http://localhost:1313/tutorials/simulating-outages/
  • Sample

[github-actions]

🎊 PR Preview has been successfully built and deployed to https://localstack-docs-preview-pr-1256.surge.sh 🎊

[SimonWallner]

what is a configuration and what is a rule?

[viren-nadkarni]

I have defined this on line 46:

Service faults can be configured using the endpoint at /_localstack/chaos/faults.
The configuration schema consists of an array of one or more rules, where each rule specifies the conditions for the fault to occur.
When active, rules are evaluated sequentially on every request to LocalStack until the first match.

Is it unclear?

[SimonWallner]

ah, now I see that the payload accepts an array. so this array would be the configuration and each element a rule?

that would mean that a configuration is identified by an id, and GET ./chaos/faults would return the configs with their ids? To update a configuration I'd then PATCH ./chaos/faults/<configuration_id>

similarly for the rules there is a DELETE so I'd assume they are also identified by an id DELETE ./chaos/faults/<fault_id>/<rule_id>

but maybe I'm thinking to complicated here... 🤔 having all that auto generated with make things much easier :D

[viren-nadkarni]

There is just one configuration. Multiple configurations are not supported.

[SimonWallner]

ok, then I guess just needs to be updated

GET: Get current configuration
POST: Add new configuration
PATCH: Add a rule
DELETE: Delete a rule

maybe a GET and PUT is sufficient here then. instead of the term 'configuration' just 'list of rules' might be easier to understand.

[SimonWallner]

briefly went through changes and comments since my last review. It's a good first step and to be extended in the near future.

[tinyg210]

LGTM overall. left 2 comments, but i think the label/tag one is more important.