Aws-syndicate

Latest version: v1.14.1

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 11

1.2.2

- Resolve available instance types from `botocore` data

1.2.1

- Added new supported EC2 instance types: `c7g`, `t4g`, `t3`

1.2.0

- Added `transform` command that creates a CloudFormation or Terraform template based on the `build_meta` of your project

1.1.1

- improve python artifacts building process. By default,
`manylinux2014_x86_64` is used for M1 and Windows. In case the platform
is set and pip installation fails, the Syndicate will try to install
a package the default way.

1.1.0

Added
- `snap_start` support of Java-based lambda configurations of
`PublishedVersions` or `None` values.
- `resourceGroup` annotation parameter to Java-based lambda.
- Specify target AWS Lambda platform, python version and implementation to install dependencies

1.0.0

Changed
- `init` command was replaced with `generate config`
- Interface of command was improved, `access_key` and `secret_key` params made optional
- Removed `account_id` param and provided ability to resolve it by STS or instance profile
- `python_build_mapping`, `java_build_mapping`, `nodejs_build_mapping` was removed as they will be resolved using the `.syndicate` file
- `generate lambda` command was improved, `common` and `tests` module for python runtime is generated with the first lambda. They contain basic common class all lambdas and simple initial test case.
- Provided ability to add information about created lambda to `.syndicate` file
- Added `test` command that allows to run tests inside your python project
- Added `profiler` command that allows to display application Lambda metrics
- Fixed an issue in `clean` command, associated with API Gateway skipping removing Lambda trigger permissions
- Fixed an issued in `clean` command associated with removing EC2 instances
- Fixed an issue in `clean` command, associated with removing resources if they specified as excluded
- Add ANY, PATCH to supported methods in API Gateway
- Changed logs format. All the logs are saved up to the path from SDCT_CONF variable if it exists. Otherwise the logs are saved to user's home directory.
- Added validation of `bundle_bucket_name` when generating config
- Added prefix and suffix validation when generating config. Their length must be less or equal to 5
- Fixed bugs with no output from `update` command
- Unified datetime format to ISO8601
- Changed `.syndicate` events saving algorithm: 30-days old events are deleted after each updating of the file. But 20 events (or less if there aren't this many) will be kept anyway, so if some amount of events exist, it isn't possible to get them all deleted.
- Added `latest_event` field to `.syndicate` file to keep the latest action's info such as: operation type, `bundle_name`, `deploy_name`, performing time and other
- Fixed generating building and deploying java and nodejs lambdas. Updated `pom.xml` template according to the new version of `deployment-configuration-annotation` plugin
- Fixed an issue when build meta is validated before resolving aliases in it
- Added `minimum_compression_size` param to API gateway deployment_resource declaration. It enables payload compression for an API with given size;
- Added lambda URL support;
- Added lambda ephemeral storage support;
- Added an ability to create DynamoDB in on-demand mode if `read_capacity`
and `write_capacity` are not specified;
- Describe an existing Api Gateway instead of creating a new one;
- Added an ability to create models in API Gateway;
- Added AWS Kinesis Firehose support;
- Add lambda event-source-mapping filters support;
- Added an ability to build lambda layers (similarly to lambdas)

Page 8 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.