api gateway endpoint configuration support#1160
Conversation
fe1cd84 to
d4d6f47
Compare
Codecov Report
@@ Coverage Diff @@
## master #1160 +/- ##
==========================================
+ Coverage 95.81% 95.81% +<.01%
==========================================
Files 28 28
Lines 4973 5021 +48
Branches 626 636 +10
==========================================
+ Hits 4765 4811 +46
- Misses 135 136 +1
- Partials 73 74 +1
Continue to review full report at Codecov.
|
42e6d4d to
5f3f76a
Compare
stealthycoin
left a comment
There was a problem hiding this comment.
Looks good to me, just one comment about docs.
5f3f76a to
bc03e60
Compare
|
ci is failing because with the websocket addition, new additions to planner end up going above the module size limit. I don't see many options here beyond disable this check globally for pylint |
bc03e60 to
4c3b37b
Compare
kyleknap
left a comment
There was a problem hiding this comment.
I just wanted to post some feedback that can be addressed. Just capturing some of the offline discussion we had...
In short the new configuration option, looks good to me. However for private api gateway, it seems like there needs to be configuration on the api gateway policy to get this all to work (we still need to confirm this). This would means we probably would want to expose a vpc endpoint id as a configuration option to auto-inject a policy and also probably expose the ability to provide a policy in the .chalice/config.json file. If it ends up being that we do need a policy applied, it may make sense to scope this PR down to regional endpoint types. Then make two subsequent PR's to support api policy and then private api's in order to narrow the scope of the PR's and not completely block support for regional endpoints.
7eace46 to
91d4c67
Compare
|
i went ahead and disabled the PRIVATE endpoint type (with validation) for a followup branch that will expose api policy and configuring private endpoint types. [update] per comments below, i went ahead and added in private endpoints back into the branch with auto or manual policy configuration and vpce config. |
922096f to
b1d10bc
Compare
2fd7d12 to
0b2268a
Compare
…h current endpoint
0b2268a to
0657b87
Compare
|
fwiw, addressed review comments and did some manual verification, change from review are in the second commit. |
386b065 to
0a99f48
Compare
|
i went ahead and added in support for private endpoints and automated or manual policy config to this pr. |
0a99f48 to
2b303d5
Compare
7eb0d61 to
aa3e706
Compare
1cc1e4a to
13d5e74
Compare
13d5e74 to
117adae
Compare
kyleknap
left a comment
There was a problem hiding this comment.
Looks good. Thanks for adding the vpce and APIG policies support. I mainly had ideas/feedback on these newly added configuration options.
845aeae to
2f0038e
Compare
3bb06a1 to
b86b569
Compare
b86b569 to
314ab78
Compare
kyleknap
left a comment
There was a problem hiding this comment.
Awesome! This looks great to me. Thanks for all of the work on this. Merging
Closes #956
Closes #897
Closes #976
Support configuring and updating the api gateway endpoint type (EDGE (default), REGIONAL, PRIVATE).
Support configure api gateway resource policy, with additional provisions for automatic policy construction in case of PRIVATE endpoints if VPC Endpoint is configured (else a manually specified policy is required).
Note for PRIVATE endpoints this does not create a vpc endpoint, which needs to be created out of band. A single vpc endpoint can be used for multiple apis though, so its one time per region config per account.