Çağrı Ekin

aws_iot_topic_rule can't update kafka action

3

### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do...

It's possible to define 2 request blocks with the same name. First one gets to executed each try. Output an error and stop execution before executing any requests or tests.

As shown in any example of chain requests, dns only resolved once and connection is re-used. In some cases someone might wish to disable this feature. A new flag needed...

`restbeast migrate ../path/to/openapi.yml` should read the openapi spec file and generate requests, hcl files. - Migrate command should discover it's an openapi file from the contentes of the file.

`restbeast scaffold METHOD` command should create a new file with an empty request block in it. Details TBD

- Possible circular dependency

- AWS Provider initial work - SSM as secret engine

Reference: https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html Example config: ```hcl request example { auth { aws4 { region = "us-east-1" service = "s3" key = "access key ID" secret = "derived signing key" } }...

- Add a retry (count int) option, that can retry for x amount if response status code isn't 2xx. - Add a delay (ms int) option that would kick in...

In context of; ``` request create-user { ... } ``` `restbeast r cre{TAB}` should result with `restbeast r create-user` `restbeast ar cre{TAB}` should result with `restbeast ar create-user`