sylvainmetayer / alias-gandi-angular Goto Github PK

https://httptoolkit.tech/blog/netlify-function-error-reporting-with-sentry

• test AWS Lambda
• host Angular app on Github page
• see Terraform or ansible for Lambda provision

Because this is not a very nice one

Quick fix but this is not good : move dev dependencies to dependencies.

Need to set NODE_ENV to something else than production so netlify can build correctly the site on master branch

Related commits

• b193b29
• b93d699
• 461ae83

• mock
• auth
• domains which should return more data and not just an array
• mailboxes which should return mailboxes ready and not just ids
• mailbox
• aliases should only have in body the aliases we want to update, not the id and domain, which are already present in query parameters

This will impact Angular API Service as well

• Change API Service
• Do not make more call than necessary

If token is invalid (expired) authentication seems to be asked twice.

https://gist.github.com/vladimirze/960d8c721455333a154fa1f73b412d51

https://brianflove.com/2017/07/17/angular-delete-confirmation/

Current behaviour :

Sent aliases update request, and if no error, add without checking back to server.

The behaviour should be the following :

Sent aliases update request, and serverless function respond with updated alias. So if an error occurs, we know it (alias is not added)

some links :

• https://www.sohamkamani.com/blog/javascript/2018-06-24-oauth-with-node-js/
• https://github.com/axa-group/oauth2-mock-server
• https://www.nexworld.fr/securiser-api-oauth2/
• https://jwt.io/
• https://medium.com/@nilasini/id-token-vs-access-token-17e7dd622084
• https://docs.gandi.net/en/rest_api/oauth2/using_oauth2_server.html
• https://serverless.com/blog/strategies-implementing-user-authentication-serverless-applications/
• https://www.jvandemo.com/how-to-use-environment-variables-to-configure-your-angular-application-without-a-rebuild/

• Present project
• How to set up dev environnment
• How to add provider