Skip to content

Latest commit

 

History

History
125 lines (100 loc) · 6.07 KB

CHANGELOG.md

File metadata and controls

125 lines (100 loc) · 6.07 KB
Raw

Change log

This is the changelog for AWS Architect.

6.7

  • Fix handlers for /route and /route/ so that the index.html is always duplicated.
  • Add support for organizational stack set deployment
  • Remove invalid regions from organizational deployment [eu-central-2, ap-south-2, eu-south-2, me-central-1, ap-southeast-4]
  • Support pnpm lock files
  • Support the new version of openapi-factory 5.4.
  • Duplicate all .html files as cleaned files. file.html => file and file/, all three will work
  • Fix validateTemplate so that it actually uses S3 when available.
  • Add support for new status CONFIGURATION_COMPLETE
  • Add missing tags properties to all interfaces.

6.6

  • Add support to deleteWebsiteVersion(version)
  • Fix The function must be in an Active state. The current state for function arn:aws:lambda:Function:514 is Pending.
  • Automatically delete existing ROLLBACK_COMPLETE stacks.
  • Add Ipv6 records to the cloudformation templates.

6.5

  • Support APIGW version 2

6.4

  • Add stackset support for AWS to cross regions
  • Skip stack deployment if template body already matches stack

6.3

  • Automatically delete the stage lambda alias and version when deleting a stage by passing in the lambda function name as the second parameter to awsArchitect.removeStagePromise.
  • Add support for all mime-types for S3 uploads

6.2

  • Allow setting upload zip file directly to support creating lambda layers
  • Add publishZipArchive to publish layers and other zip files directly to S3, using the package name and version automatically.
  • New option in publishLambdaArtifactPromise to allow turning off running npm or yarn for package deployment autoHandleCompileOfSourceDirectory = false.
  • Now uploads to the S3 directory file that matches any directory that contains an index.html for automatic redirects to the index.html.

6.1

  • Deploy CF templates to S3 deployment bucket before deploying to CF to increase allow size of templates to 450KB.
  • Allow cache control to be the full string, not just an number
  • Dynamically inject http and api subpath into Location urls.
  • cacheControlRegexMap supports array to keep order of regex mappings
  • deployTemplate StackConfiguration options now accepts automaticallyProtectStack which defaults to be true, to protect stacks. This will only protect stacks which are successfully created.

6.0

  • Remove hosting index html, recommendation is to use nodemon and serve for that.
  • Removed deprecated methods
  • Now supports calling schedule and event triggers locally via the REST api.
  • Nodejs8.10 by default
  • Auto increment port starting at 8080 or specified up to 10 ports before falling back to a random port.
  • Use -s in stage names instead of _ so that more CIs can match their environments stages correctly.
  • Added default override for S3 content type uploads.
  • Allow deploying .files using the bucketManager
  • Dynamically inject http and api subpath into url hrefs.
  • Remove autocreation of api gateway when attempting to find it. The expectation is that "searching for the API" happens always after the CF stack creation.
  • awsArchitect.run now returns the server which contains the only method stop allowing manual shutdown.

5.1

  • Provide lower case names for methods.
  • Add deprecation warning to removal methods in 6.0.
  • Index.html is uploaded last.
  • Add in dynamic resolving of ACM certs by domain name.

5.0

  • Upgrade to OpenAPI-factory 3.0, see openapi factory for breaking changes. This means that the authorizer now takes event and the authorization token must be manually extracted.
  • Support authorizer resolution in express server.run
  • Allow providing a custom logger to run function.

4.2

  • Include cloud formation deployment for standard resources.
  • Added example cloud formation template to template service.
  • New RemoveStage in AWS Architect.
  • Add Support for yarn.lock files by assuming yarn should be executed.

4.1

  • Add +AwsArchitect.prototype.publishLambdaArtifactPromise to perform the action to deploy a microservice zip package to S3.
  • Allow specifying S3 artifacts cache-control times as overrides.

4.0

  • Removed passing the bucket as configuration into publishWebsite. Bucket is required as part of contentOptions.
  • Prevent overwriting the bucket configuration using the options parameter in publishWebsite.

3.7

  • Default to region set in aws config, rather than us-east-1.

3.6

  • Allow sending binary Buffer bodies via local server to match API Gateway functionality.

3.5

  • Upgrade default nodejs version to 6.10.

3.4

  • Upgrade jwt resolution to include by default RS256.

3.3

  • Remove CORS headers from local server.

3.2

  • Automatically create the service role to execute the lambda functions.
  • Automatically create the s3 bucket with the website policy if it doesn't exist.

3.1

  • Moved website bucket configuration to contentOptions.
  • Added AwsArchitect.promoteToStage(source, stage) function which will copy a bucket directory.

3.0

  • Upgrade to handle ANY on aws resources.
  • Allow running just a website on port 8080, without any extra api files.

2.1

  • Add support for creating dynamoDB Tables.
  • Separate policy examples into their own documents.
  • Allow specifying specific port to run on.
  • Deploy content directory to s3.

2.0

  • All configuration is now contained in the api files. Generation, run, and testing is completed via index.js. New templates created.
  • A single lambda function is created, for the purpose of the whole microservice.
  • Introduced configuration options for the api and content (s3).

1.1

  • Lambdas are not all specified in the file specified by the constructor call. Default is the src/index.js file in make.js. aws-config.js will be removed in version 2.0, and all configuration can be specified in the index.js composition root.

1.0

  • Introduced commandline ruby tool aws-architect for configuring a AWS Microservice instance using Cloud Formation and AWS API.