This commit is contained in:
José Ivanchechen 2022-12-04 15:51:34 +00:00
parent 291ba01894
commit 7a50a6b085
2 changed files with 3 additions and 3 deletions

View File

@ -3,7 +3,7 @@ params:
ShowCodeCopyButtons: true ShowCodeCopyButtons: true
homeInfoParams: homeInfoParams:
Title: Hello there! Title: Hello there!
Content: Nada muito útil por aqui, só alguns projetos mesmo. Content: Nothing good around here, maybe you misclicked.
socialIcons: socialIcons:
- name: "Instagram" - name: "Instagram"

View File

@ -5,7 +5,7 @@ draft: false
summary: "How to create API Gateway endpoints with Terraform." summary: "How to create API Gateway endpoints with Terraform."
--- ---
Right when we first started to use the AWS API Gateway, one of the things that did bother us was the fact that we had to manage lot of resources, spread into 1,000s of lines of a couple of Terraform files, and it was a lot of work that required attention and time, things that are critical in software development as we all know. Right when we first started to use the AWS API Gateway, one of the things that did bother us was the fact that we had to manage lot of resources spread into 1,000s of lines of a couple of Terraform files, and it was a lot of work that required attention and time, things that are critical in software development as we all know.
So we decided to create a module to help us with this. Big thanks to [Stephano](https://www.linkedin.com/in/stephano-macedo/) who helped me a lot! So we decided to create a module to help us with this. Big thanks to [Stephano](https://www.linkedin.com/in/stephano-macedo/) who helped me a lot!
@ -232,7 +232,7 @@ For one endpoint, we went from having to manage 15 lines splitted in 3 files to
## WWW-Authenticate header ## WWW-Authenticate header
We can also add the `WWW-Authenticate` header to the request for example. We tried to do that by adding it to the files properly, but it didn't work. The reason was that the API Gateway was not passing the `WWW-Authenticate` to our API, and that's because of the name of the header. You can call it `WWW-Authenticate-Header` for example and it will work. We can also add the `WWW-Authenticate` header to the request for example. We tried to do that by adding it to the files properly, but it didn't work. The reason was that the API Gateway was not passing the `WWW-Authenticate` to our API, and that's because of the name of the header. You can call it `WWW-Authenticate-Header` for example and it will work.
## Disclaimer ## Note
This code has not been tested "as is", but it has been tested as part of a bigger project. There is always room for improvements and more possibilities depending on the context, but it's a good start. This code has not been tested "as is", but it has been tested as part of a bigger project. There is always room for improvements and more possibilities depending on the context, but it's a good start.
There has been a lot of pieces of Terraform code that was omitted, like when we use the declare the `terraform_remote_state` or the `authorizer_id` which you will need if using authorization "CUSTOM". There has been a lot of pieces of Terraform code that was omitted, like when we use the declare the `terraform_remote_state` or the `authorizer_id` which you will need if using authorization "CUSTOM".