Skip to content

Release 0.47.26

Compare
Choose a tag to compare
@aws-sdk-dotnet-automation aws-sdk-dotnet-automation released this 17 Jun 02:00
· 253 commits to main since this release
8125cac

0.47.26

Bug Fixes

  • Add validation for EC2 instance types for Elastic Beanstalk recipes
  • Do not validate against terminated Beanstalk environments
  • Escape hyphen(-) in the image tag regex validator
  • Fixed environment variables not being set correctly in AWS App Runner deployments
  • Fixed issue with deserialize types that do not have a parameterless constructor.
  • Add AWS.Deploy.Recipes.CDK.Common to force building the project and create nupkg
  • Create bootstrap template fails if directory doesn't exist
  • Deployment bundle settings don't have a fully qualified id
  • Failed setting updates in server mode return setting value instead of ID
  • Proper cdk version is not installed in the local deployment project directory
  • Recipe validators are not run in server mode
  • Subnets and security groups are displayed without selected vpc id in app runner BREAKING CHANGE: Users that had a VPC Connector added to the deployment need to opt back into the feature as deployments will now set UseVPCConnector to false by default.

Documentation

  • Added an initial version of the deploy tool documentation

Features

  • Add .NET 6 as a target framework for CLI to support M1 Macs
  • Add URI validator and set default value for resource path pattern in the Blazor recipe
  • Add string length validator to ECR repository name
  • ApplyConfigSettings API now rejects updating readonly settings
  • Reduce AWS.Deploy.Tools NuGet packaged down to 5 megs from 63 megs
  • Update supported target frameworks to include .NET 7 for container based recipes and remove support for EOL .NET Core 2.1
  • Add validators to check if Subnets and Security Groups are part of the same VPC
  • Added validator to check if health check interval is greater than timeout
  • Update VPCs in all recipes to match app runner recipe BREAKING CHANGE: Anyone using a VPC in their current deployment will not be able to add a VPC after they perform a redeployment. You will need to delete the existing stack and deploy a new one.

CI Configuration Changes

  • Add PR check to make sure RestApi client is updated

Build System or External Dependencies

  • Version bump to 0.47

BREAKING CHANGE

Removed support for deploying .NET Core 2.1 applications