Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate the redirect source(s) in bin/ before instantiating the stack #2

Open
douglasnaphas opened this issue Oct 13, 2021 · 2 comments

Comments

@douglasnaphas
Copy link
Contributor

No description provided.

@douglasnaphas douglasnaphas created this issue from a note in sredirect-v1 (To do) Oct 13, 2021
@douglasnaphas douglasnaphas changed the title Validate the redirect target in bin/ before instantiating the stack Validate the redirect source(s) in bin/ before instantiating the stack Oct 13, 2021
@douglasnaphas
Copy link
Contributor Author

I actually don't think I need extensive validation of the account's rights over the source domain, because if the account doesn't have them, stack deployment will fail when we can't get a cert.

@douglasnaphas
Copy link
Contributor Author

Note: when you create a hosted zone for a name you don't own, AWS creates a delegation set of name servers associated with that hosted zone. I proved this out in my lab2 account.

douglasnaphas added a commit that referenced this issue Feb 5, 2022
douglasnaphas added a commit that referenced this issue Feb 5, 2022
douglasnaphas added a commit that referenced this issue Feb 5, 2022
gh-2

I am losing track of what type my various objects representing the input
params are.
douglasnaphas added a commit that referenced this issue Feb 5, 2022
douglasnaphas added a commit that referenced this issue Feb 6, 2022
douglasnaphas added a commit that referenced this issue Feb 6, 2022
gh-2

SSM Params have a size limit of 4096 bytes each. I might switch to
having one param per redirect or HTTP origin for this reason.
douglasnaphas added a commit that referenced this issue Feb 6, 2022
gh-2

I'm going to do both 302s and fronting of HTTP Origins.
douglasnaphas added a commit that referenced this issue Feb 6, 2022
gh-2

This includes a pretty infuriating issue relating to "const enum" vs
"enum." I got an error:

TypeError: Cannot read properties of undefined (reading 'FOUND')

before I changed `export enum` to `export const enum`, which is
seriously confusing.

https://stackoverflow.com/questions/50365598/typescript-runtime-error-cannot-read-property-of-undefined-enum
douglasnaphas added a commit that referenced this issue Feb 7, 2022
douglasnaphas added a commit that referenced this issue Feb 7, 2022
douglasnaphas added a commit that referenced this issue Feb 7, 2022
douglasnaphas added a commit that referenced this issue Feb 9, 2022
douglasnaphas added a commit that referenced this issue Feb 9, 2022
gh-2

I want type errors, which here I mean to include "that's a URL with no
scheme," to fail in bin, not lib. My last build, which ran with a
from-value with no scheme (like "https://") failed in lib.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant