feat(parser): add support for Lambda Function URL

[ran-isenberg]

Issue number: #1425

Summary

Changes

added envelope and model for lambda function url as described at #1425

fixed a bug in api gwv2 model where cognitoIdentity wasnt optional.

I was unable to fix the docs for the parser due to a linter bug, will open an issue.

User experience

Can now use an envelope for lambda function url or extend the model.

Is this a breaking change? No.

RFC issue number:
#1425
Checklist:

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[ran-isenberg]

@heitorlessa i wasnt able to push the docs update.
They pass the docs-linter stage but fail on the pre-commit on this error:
docs/utilities/parser.md:586 MD043/required-headings/required-headers Required heading structure [Context: "## Getting started"]

[leandrodamascena]

Hi @ran-isenberg.. I'm refactoring all examples and for now you can add this comment after the description line..

<!-- markdownlint-disable MD043 -->

like this: 7be425e#diff-aa083264efcaf3125cc0560e9b88cce2c69e4becd8ea39211057634ec3f56bd9R6

[heitorlessa]

Thanks a lot @ran-isenberg !! As @leandrodamascena shared, this is the new doc linting to enforce a consistent style, you can ignore for now with that string at the top of the file since we're refactoring all of it (structure, snippets to be way more realistic, run as-is).

@leandrodamascena could you please fix that mypy issue by installing snappy as a dev dependency and ignoring the lack of types for snappy? We missed in the last PR as I accidentally didn't allow GH Actions to run (part of the new repo hardening)

[ran-isenberg]

pushed the docs ;)

[ran-isenberg]

@heitorlessa it failed on the snappy stuff. I updated from develop branch, hopefully it will work now

[heitorlessa]

Yes it was fixed on #1446, my other PR was impacted and working after the merge

…

On Fri, 12 Aug 2022 at 08:20, Ran Isenberg ***@***.***> wrote: @heitorlessa <https://github.com/heitorlessa> it failed on the snappy stuff. I updated from develop branch, hopefully it will work now — Reply to this email directly, view it on GitHub <#1442 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBGY3STSYALQBFFT4I3VYXUKFANCNFSM56IX7WWQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[codecov-commenter]

Codecov Report

Merging #1442 (ddf1dd1) into develop (0e20ee0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop    #1442   +/-   ##
========================================
  Coverage    99.89%   99.89%           
========================================
  Files          121      123    +2     
  Lines         5479     5496   +17     
  Branches       627      629    +2     
========================================
+ Hits          5473     5490   +17     
  Misses           2        2           
  Partials         4        4           

Impacted Files	Coverage Δ
..._powertools/utilities/parser/envelopes/__init__.py	100.00% <100.00%> (ø)
.../utilities/parser/envelopes/lambda_function_url.py	100.00% <100.00%> (ø)
...bda_powertools/utilities/parser/models/__init__.py	100.00% <100.00%> (ø)
...mbda_powertools/utilities/parser/models/apigwv2.py	100.00% <100.00%> (ø)
...ols/utilities/parser/models/lambda_function_url.py	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[heitorlessa]

@rubenfonseca assigned it to you as you fixed the quirks of Function URL.

@ran-isenberg CI passed. Ruben is back on Monday from holidays and should get this reviewed and merged next week.

Thank you again

[rubenfonseca]

Just rebased with master before the review

[rubenfonseca]

Hi @ran-isenberg thank you for this! Just left two small suggestions. Let me know if it makes sense so we can merge.

[leandrodamascena]

Hi @ran-isenberg thank you for this! Just left two small suggestions. Let me know if it makes sense so we can merge.

Hi!! Just in case of better understanding of the project I did a double check and everything seems fine to merge. I ran these changes locally and it went fine.

[ran-isenberg]

@heitorlessa waiting for the merge :)

[heitorlessa]

@rubenfonseca will be merging ;) Thanks a lot everyone!!

[rubenfonseca]

Thanks again Ran! Can't wait to get this out soon :)