Closed KenSentMe closed 7 months ago
Is there any error on deploy/update?
None that I can see. We set up Github actions for deploy/update. This is the last bit of the output:
Packaging project as zip.
Uploading xxx-production-1700735655.tar.gz (134.7MiB)..
0%| | 0.00/141M [00:00<?, ?B/s]
0%| | 262k/141M [00:00<05:03, 465kB/s]
1%| | 1.05M/141M [00:00<01:16, 1.84MB/s]
2%|▏ | 2.36M/141M [00:00<00:35, 3.96MB/s]
3%|▎ | 4.46M/141M [00:00<00:18, 7.22MB/s]
4%|▍ | 6.29M/141M [00:01<00:14, 9.08MB/s]
6%|▌ | 8.65M/141M [00:01<00:14, 9.19MB/s]
9%|▉ | 12.8M/141M [00:01<00:08, 15.2MB/s]
13%|█▎ | 18.1M/141M [00:01<00:05, 23.1MB/s]
19%|█▉ | 26.5M/141M [00:01<00:03, 37.3MB/s]
24%|██▍ | 34.1M/141M [00:01<00:02, 46.6MB/s]
33%|███▎ | 46.9M/141M [00:01<00:01, 67.6MB/s]
44%|████▍ | 62.1M/141M [00:01<00:00, 89.4MB/s]
56%|█████▌ | 78.4M/141M [00:02<00:00, 109MB/s]
68%|██████▊ | 95.7M/141M [00:02<00:00, 125MB/s]
77%|███████▋ | 109M/141M [00:02<00:00, 105MB/s]
77%|███████▋ | 109M/141M [00:02<00:00, 94.4MB/s]
86%|████████▌ | 121M/141M [00:02<00:00, 97.4MB/s]
95%|█████████▍| 134M/141M [00:02<00:00, 104MB/s]
100%|██████████| 141M/141M [00:03<00:00, 45.8MB/s]
Uploading handler_xxx-production-1700735774.zip (17.8MiB)..
0%| | 0.00/18.7M [00:00<?, ?B/s]
1%|▏ | 262k/18.7M [00:00<00:16, 1.11MB/s]
3%|▎ | 524k/18.7M [00:00<00:10, 1.77MB/s]
48%|████▊ | 8.91M/18.7M [00:00<00:00, 23.2MB/s]
49%|████▉ | 9.18M/18.7M [00:00<00:00, 40.2MB/s]
80%|████████ | 15.0M/18.7M [00:00<00:00, 39.1MB/s]
100%|██████████| 18.7M/18.7M [00:00<00:00, 21.6MB/s]
Updating Lambda function code..
Waiting for lambda function [xxx-production] to be updated...
Updating Lambda function configuration..
Uploading xxx-production-template-1700735792.json (1.7KiB)..
0%| | 0.00/1.71k [00:00<?, ?B/s]
100%|██████████| 1.71k/1.71k [00:00<00:00, 8.31kB/s]
100%|██████████| 1.71k/1.71k [00:00<00:00, 8.28kB/s]
Deploying API Gateway..
Scheduling..
Unscheduled xxx-zappa-keep-warm-handler.keep_warm_callback.
Scheduled xxx-zappa-keep-warm-handler.keep_warm_callback with expression rate(4 minutes)!
Waiting for lambda function [xxx-production] to be updated...
Your updated Zappa deployment is live!: https://xxx.execute-api.eu-central-1.amazonaws.com/production
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.
Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.
Context
We use zappa to deploy our Django api. I wanted to enable caching on one of the endpoints in API Gateway. In API Gateway I created the required resources and GET method and linked it to my Lambda function. After that in the Method request tab I created the necessary URL query string parameters and in the Integration request tab enabled Lambda proxy integration.
This all works fine. Requests with a given query parameter are cached correctly. However, when I run
zappa update
to push some new code, the method I created isn't working anymore. To get it working again, I have to remove the method, create it again and the deploy it (all is done in API Gateway). Is there a way to circumvent this using Zappa or should I look into AWS settings for this?Expected Behavior
I expect the endpoint method to keep working, because no setting has changed (I re-create the method with the exact same settings)
Actual Behavior
See above
Your Environment
pip freeze
:zappa_settings.json
: