clear-skies-aws 1.9.13__py3-none-any.whl → 1.9.14__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. {clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/METADATA +1 -1
  2. {clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/RECORD +5 -5
  3. clearskies_aws/input_outputs/lambda_invocation.py +3 -1
  4. {clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/LICENSE +0 -0
  5. {clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/WHEEL +0 -0
{clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/METADATA RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: clear-skies-aws
3
- Version: 1.9.13
3
+ Version: 1.9.14
4
4
  Summary: clearskies bindings for working in AWS
5
5
  Home-page: https://github.com/cmancone/clearskies-aws
6
6
  License: MIT
{clear_skies_aws-1.9.13.dist-info → clear_skies_aws-1.9.14.dist-info}/RECORD RENAMED
@@ -40,7 +40,7 @@ clearskies_aws/input_outputs/lambda_api_gateway_test.py,sha256=1I8yV-WjKUKpoMZa2
40
40
  clearskies_aws/input_outputs/lambda_api_gateway_web_socket.py,sha256=kG2fys9X7TailvlOBzIMItuSI8rlvDbBD4AXtI091hM,308
41
41
  clearskies_aws/input_outputs/lambda_elb.py,sha256=b675h0DxTGo9YscXN4mwzRGzP3hNSie4iPRKOg3kKPI,750
42
42
  clearskies_aws/input_outputs/lambda_http_gateway.py,sha256=YQk7GlQWtQjDiKWhX5jvXc3un1eq2sm1v_jl6iseNoQ,692
43
- clearskies_aws/input_outputs/lambda_invocation.py,sha256=YB1DvtpOAQjIZ6Vu-vAecbbkHQ9YheGMYHAZozN4Dzs,928
43
+ clearskies_aws/input_outputs/lambda_invocation.py,sha256=yF3rYJ-r0YYzlh--33fGE-I-pzyhQxDmDo1TUQxCu00,1122
44
44
  clearskies_aws/input_outputs/lambda_sns.py,sha256=t1iWH1OaOm23ZSQoKgS6l53FTExFziPVju3wf86D0WY,2266
45
45
  clearskies_aws/input_outputs/lambda_sqs_standard.py,sha256=8UlYNi3DHZB9i8OXy8LsM13OIHtbOFxVh-LvyNN0yao,2185
46
46
  clearskies_aws/mocks/__init__.py,sha256=mn764gINN667tYoJfnsM6HjAAhCsO_kZ6E-fUwdLY50,22
@@ -61,7 +61,7 @@ clearskies_aws/secrets/parameter_store_test.py,sha256=UyqKE4AZYlldj9ww5f0fR15qsV
61
61
  clearskies_aws/secrets/secrets_manager.py,sha256=jlpfAFC23EeSpm50L8B-yrXg4IROQq-M_90zzXDp_ak,3056
62
62
  clearskies_aws/secrets/secrets_manager_test.py,sha256=mlNWtDm1wWS5C8aV0vJAzZVZB82KFR6NGRAPEkLtTyk,786
63
63
  clearskies_aws/web_socket_connection_model.py,sha256=d_Au_Pu7YXBfc7_lbuI7zz4MZ8ZOOwGM0oooppEofcI,1776
64
- clear_skies_aws-1.9.13.dist-info/LICENSE,sha256=3Ehd0g3YOpCj8sqj0Xjq5qbOtjjgk9qzhhD9YjRQgOA,1053
65
- clear_skies_aws-1.9.13.dist-info/METADATA,sha256=1RFOINl2a5ar7NqszZYfzerQ6lSp0KH9TynbpvNyBHM,8583
66
- clear_skies_aws-1.9.13.dist-info/WHEEL,sha256=Nq82e9rUAnEjt98J6MlVmMCZb-t9cYE2Ir1kpBmnWfs,88
67
- clear_skies_aws-1.9.13.dist-info/RECORD,,
64
+ clear_skies_aws-1.9.14.dist-info/LICENSE,sha256=3Ehd0g3YOpCj8sqj0Xjq5qbOtjjgk9qzhhD9YjRQgOA,1053
65
+ clear_skies_aws-1.9.14.dist-info/METADATA,sha256=gPkZNsxHvCkVWlFvRQ14clUyY4qI7rACNt95gLHRbgA,8583
66
+ clear_skies_aws-1.9.14.dist-info/WHEEL,sha256=Nq82e9rUAnEjt98J6MlVmMCZb-t9cYE2Ir1kpBmnWfs,88
67
+ clear_skies_aws-1.9.14.dist-info/RECORD,,
clearskies_aws/input_outputs/lambda_invocation.py CHANGED
@@ -23,7 +23,9 @@ class LambdaInvocation(LambdaAPIGateway):
23
23
  def get_body(self):
24
24
  return self._event
25
25
 
26
- def json_body(self, required=True):
26
+ def json_body(self, required=True, allow_non_json_bodies=False):
27
+ # we ignore the allow_non_json_bodies flag here because with the way invoking lambdas works,
28
+ # the event already is an object, so it's a moot point.
27
29
  if required and not self._event:
28
30
  raise ClientError("Request body was not valid JSON")
29
31
  return self._event