You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 🔧 update for case where expected metadata for given package does not contain 'releases'
* :penicl: add warning for case where expected `package_version` is not found.
* 🔧 change pipenv req to version greater than previously reported problem version.
* 🙈 Add `Pipfile.lock` to `.gitignore` (When supporting multiple versions of python with pipenv don't include the lock file.
* 🔧 fix pipenv version restriction.
* 🎨 run black on `core.py`
* 🎨 fix flake8, run black
* 🔧 adjust caching (requirements.txt no longer used.
* 🐛 fix Pipfile typo
* 🔥 The python3.6 runtime is deprecated by aws (July 18, 2022 [phase-1], Aug 17, 2022 [phase-2]) remove from tests for next release candidate
* 🎨 run black
🔧 update black check command.
* 🎨 run isort
* 📝 change version 0.54.1 -> 0.55.1
🔥 remove 3.6 from SUPPORTED_VERSIONS
* 🔥 remove 3.6 support
* 🔀 merge with `0.54.2-release` branch to apply 3.9 support documentation updates.
🔥 remove 3.6 support from README
* 🔀 merge with `0.54.2-release` branch to apply 3.9 support documentation updates.
* ⏪️revert __version__ back to available pypi version
Without a pypi available release the `test_slim_handler` testcase fails.
```
ERROR: No matching distribution found for zappa==0.55.1
E...................
======================================================================
ERROR: test_slim_handler (tests.tests.TestZappa)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/runner/work/Zappa/Zappa/tests/tests.py", line 2211, in test_slim_handler
zappa_cli.create_package()
File "/home/runner/work/Zappa/Zappa/zappa/cli.py", line 2430, in create_package
venv=self.zappa.create_handler_venv(),
File "/home/runner/work/Zappa/Zappa/zappa/core.py", line 494, in create_handler_venv
raise EnvironmentError("Pypi lookup failed")
OSError: Pypi lookup failed
-------------------- >> begin captured stdout << ---------------------
```
* 📝 update CHANGELOG with committed changes since last release (5b6e241)
* 🔥 remove 3.6 from docs
* 🔧 address review comments
* ✨ change release to 0.55.1
* ♻️ Update to allow specification of the latest pypi version for `test_slim_handler()`
* ✅ update `test_slim_handler()` so that lastest pypi version is *not* hardcoded (get from "git tags" result)
* 🎨 run black/isort
* 🔧 attempt to update github action to retrieve the latest tags.
* 🔧 fix bad ci command definition
* 📝 created and added issue for python3.6 support removal.
* ✨ add `python_requires` to setup().
* 📝 fix issue #900
* 📝 add link to https://slackautoinviter.herokuapp.com to join slack. (the zappateam.slack may be private?)
* 🔥 remove `future` (past) requirements basestring usage, replacing with isinstance(x, str)
🔧 change usage of utcnow() -> datetime.datetime.now(datetime.timezone.utc)
* 🔥 Remove 'futures' package requirement (#826)
* 📝 fix issue #900
* 🔥 remove unnecessary __future__ import
🔧 Start versioning at 0; 0.55.1 -> 0.55.0
* 🎨 fix flake8
* 🐛 fix cd.yaml to only run on push of tag meeting the release tag criteria. (#1152)
* 📝 add 1152 to CHANGELOG
# on.push.tags: If you define only tags/tags-ignore or only branches/branches-ignore, the workflow won't run for events affecting the undefined Git ref.
7
+
#
8
+
# This workflow will only run when a tag matching the criteria is pushed
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ __Awesome!__
135
135
136
136
## Installation and Configuration
137
137
138
-
_Before you begin, make sure you are running Python 3.6/3.7/3.8 and you have a valid AWS account and your [AWS credentials file](https://blogs.aws.amazon.com/security/post/Tx3D6U6WSFGOK2H/A-New-and-Standardized-Way-to-Manage-Credentials-in-the-AWS-SDKs) is properly installed._
138
+
_Before you begin, make sure you are running Python 3.7/3.8/3.9 and you have a valid AWS account and your [AWS credentials file](https://blogs.aws.amazon.com/security/post/Tx3D6U6WSFGOK2H/A-New-and-Standardized-Way-to-Manage-Credentials-in-the-AWS-SDKs) is properly installed._
139
139
140
140
**Zappa** can easily be installed through pip, like so:
141
141
@@ -394,11 +394,11 @@ You can execute any function in your application directly at any time by using t
394
394
395
395
For instance, suppose you have a basic application in a file called "my_app.py", and you want to invoke a function in it called "my_function". Once your application is deployed, you can invoke that function at any time by calling:
396
396
397
-
$ zappa invoke production 'my_app.my_function'
397
+
$ zappa invoke production my_app.my_function
398
398
399
399
Any remote print statements made and the value the function returned will then be printed to your local console. **Nifty!**
400
400
401
-
You can also invoke interpretable Python 3.6/3.7/3.8 strings directly by using `--raw`, like so:
401
+
You can also invoke interpretable Python 3.7/3.8/3.9 strings directly by using `--raw`, like so:
402
402
403
403
$ zappa invoke production "print(1 + 2 + 3)" --raw
404
404
@@ -929,7 +929,7 @@ to change Zappa's behavior. Use these at your own risk!
929
929
"role_name":"MyLambdaRole", // Name of Zappa execution role. Default <project_name>-<env>-ZappaExecutionRole. To use a different, pre-existing policy, you must also set manage_roles to false.
930
930
"role_arn":"arn:aws:iam::12345:role/app-ZappaLambdaExecutionRole", // ARN of Zappa execution role. Default to None. To use a different, pre-existing policy, you must also set manage_roles to false. This overrides role_name. Use with temporary credentials via GetFederationToken.
931
931
"route53_enabled":true, // Have Zappa update your Route53 Hosted Zones when certifying with a custom domain. Default true.
932
-
"runtime":"python3.6", // Python runtime to use on Lambda. Can be one of "python3.6", "python3.7" or "python3.8". Defaults to whatever the current Python being used is.
932
+
"runtime":"python3.9", // Python runtime to use on Lambda. Can be one of "python3.7", "python3.8", or "python3.9". Defaults to whatever the current Python being used is.
933
933
"s3_bucket":"dev-bucket", // Zappa zip bucket,
934
934
"slim_handler":false, // Useful if project >50M. Set true to just upload a small handler to Lambda and load actual project from S3 at runtime. Default false.
935
935
"settings_file":"~/Projects/MyApp/settings/dev_settings.py", // Server side settings file location,
@@ -1538,6 +1538,7 @@ If you are adding a non-trivial amount of new code, please include a functioning
1538
1538
Please include the GitHub issue or pull request URL that has discussion related to your changes as a comment in the code ([example](https://github.com/zappa/Zappa/blob/fae2925431b820eaedf088a632022e4120a29f89/zappa/zappa.py#L241-L243)). This greatly helps for project maintainability, as it allows us to trace back use cases and explain decision making. Similarly, please make sure that you meet all of the requirements listed in the [pull request template](https://raw.githubusercontent.com/zappa/Zappa/master/.github/PULL_REQUEST_TEMPLATE.md).
1539
1539
1540
1540
Please feel free to work on any open ticket, especially any ticket marked with the "help-wanted" label. If you get stuck or want to discuss an issue further, please join [our Slack channel](https://zappateam.slack.com/), where you'll find a community of smart and interesting people working dilligently on hard problems.
1541
+
[Zappa Slack Auto Invite](https://slackautoinviter.herokuapp.com)
1541
1542
1542
1543
Zappa does not intend to conform to PEP8, isolate your commits so that changes to functionality with changes made by your linter.
0 commit comments