Formatting

guides/quickstart/quickstart.md

@@ -146,7 +146,7 @@ Start MultiTool Canary to upload your new lambda version and start monitoring tr
 In order to see MultiTool Canary in action, we'll need to simulate some traffic to our API endpoint. We can do that autoamtically with a tool like [Bombardier](https://github.com/codesenberg/bombardier) or manually with an API Client like [Bruno](https://www.usebruno.com/) or [Postman](https://www.postman.com/)
 
 ```bash
-$ canary deploy --aws-apig-name ${MY_APIGATEWAY_NAME} --aws-apig-stage ${MY_APIGATEWAY_STAGE} --aws-lambda ${MY_LAMBDA_NAME} --aws-resource-name ${MY_RESOURCE_NAME} --aws-resource-method ${MY_RESOURCE_METHOD} out.zip
+$ canary deploy --aws-apig-name ${MY_APIGATEWAY_NAME} --aws-apig-stage ${MY_APIGATEWAY_STAGE} --aws-lambda ${MY_LAMBDA_NAME} --aws-resource-path ${MY_RESOURCE_NAME} --aws-resource-method ${MY_RESOURCE_METHOD} out.zip
 
 $ watch -n 30 bombardier -c 5 -n 50 ${MY_URL} | grep "HTTP codes:" -A 1 | tail -n +2
 ```

src/config/deploy/mod.rs

@@ -22,5 +22,5 @@ pub struct DeploySubcommand {
     pub aws_resource_path: String,
     /// The HTTP method of the AWS API Gateway Resource
     #[arg(long, env = "MULTI_AWS_RESOURCE_METHOD")]
-    pub aws_resource_method: String,
+    pub aws_resource_method: String, //TODO: make this an Enum since the values are fixed
 }