Releases: aws/aws-dotnet-deploy
Releases · aws/aws-dotnet-deploy
Release 0.49.14
0.49.14
Bug Fixes
- Fix integration tests failure from setting a custom workspace
- Refactor config file deployment workflow
- Throw an exception when attempting to generate a Dockerfile with project references located outside of the solution directory
Documentation
- Add additional troubleshooting guide entries for docker build issues
- Add emoji support to the docs website
- Fix broken link in the troubleshooting guide
- Fix broken link in the troubleshooting guide
- Remove statement that says project is in developer preview status
CI Configuration Changes
- Add GitHub Action to detect new CDK Bootstrap template versions
Chore
- Update GitHub issue/feature forms and automation
- Update all recipe versions to 1.0.0
- Update the CDK Bootstrap template to the latest version
Build System or External Dependencies
- Version bump to 0.49
BREAKING CHANGE
The option setting items in the deployment settings file are now specified by the 'Settings' JSON property instead of 'OptionSettingsConfig'
Release 0.48.15
0.48.15
Chore
- Run CDK bootstrap in deploy tool workspace instead of generated CDK project
- Update Newtonsoft.Json version
- Update the supported NodeJS version from 10 to 14
Bug Fixes
- Instance type and windows platform arn type hints to accommodate recent API changes.
Features
- Add support for returning tables of options via GetConfigSettingResources in server mode. This allows wrapping tools to display richer grids/tables when presenting the user a list of options to select from. The subnets and security groups for App Runner's VPC Connector and Beanstalk Platform are supported initially.
- Add support to deploy to Elastic Beanstalk running Windows Server
- Allow users to override the default deploy tool workspace directory
- Add troubleshooting guide and cut a ticket links on exception
- Add validator to check if VPC has subnets in different AZs
- Change security groups setting in fargate to a list instead of string
Documentation
- Doc changes for Windows support with Elastic Beanstalk
- Modified short descriptions and missing dependencies text
- Modified short descriptions
Build System or External Dependencies
- Add readme to nuget packages
- Update the PR check infra to support node 14
- Use PackageOutputAbsolutePath instead to match dotnet pack --output dir
- Version bump to 0.48
Release 0.47.26
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
Release 0.46.16
0.46.16
CI Configuration Changes
- Add integration test PR check codebuild project concurrency limit
- Remove push from AWS CodeBuild CI workflow
- Update PR build to use AWS Code Build and the GitHub OpenID Connector
Features
- Add support for custom Dockerfile paths
- Add new OptionSetting validator to check for conflict with existing resources
- Only run validators if setting is displayable
- Persist invalid value in validation object of option setting item
- Run dependent settings validators when an option setting value is set
- Validators are not all run if one has a failure
Bug Fixes
- Remove AllowEmptyString from Regex validators as they allow failed deployments
Chore
- Alter application name option setting in Elastic Beanstalk recipe
- Centralize recipe creation
- Create an option setting dependency tree
Build System or External Dependencies
- Version bump to 0.46
BREAKING CHANGE
Previously DockerExecutionDirectory was treating paths
as relative to the directory where the deployment tool is running.
If you were specifying a relative Docker execution directory, adjust
it to be relative to the project path.
Release 0.45.9
0.45.9
Chore
- Add constructor injection support to option and recipe validators
- Improve error message for missing NodeJS dependency
- Add process exit code to improve telemetry of failed processes
Bug Fixes
- Check for duplicate cloud application names
- Rework the "Docker Build Args" option to support appending any options to the docker build command, instead of just
--build-arg
- Validate and respect deployment bundle settings for the Docker or dotnet builds during server mode
Features
- Add categories for all settings
Build System or External Dependencies
- Version bump to 0.45
BREAKING CHANGE
If you were previously using "Docker Build Args" to set build-time variables, you must now prepend --build-arg
for each argument yourself.
Release 0.44.9
0.44.9
Chore
- Improve error handling when creation of deployment bundle fails
- Add a service to handle Recommendations and Option Setting items
- Improve error handling for failed first time deployments
Bug Fixes
- Add ProducesResponseType for the possible error codes in ServerMode API
- Add stack name validation in server mode
- Security Group option setting in App Runner recipe has an invalid name
- Cannot use ActivatorUtilities.CreateInstance with internal class
Build System or External Dependencies
- Version bump to 0.44
Release 0.43.6
0.43.6
Features
- Skip executing "cdk deploy" if CDKToolkit stack already exists
Bug Fixes
- Add new error code to indicate deployment bundle creation failure from a generate docker file
- Add the new ReceiveLogSectionStart callback to the IDeploymentCommunicationClient
- Consolidate the separate CLI and ServerMode CreateDeploymentBundle methods into the Orchestrator
- Fixed issue with Beanstalk Application and Environment name not correctly modeled in recipe definition.
Build System or External Dependencies
- Version bump to 0.43
Release 0.42.10
0.42.10
Bug Fixes
- Amend strategy to find the source control root directory
- Handle invalid project paths with appropriate exception
- Rename the "ECR Repository Name" advanced option to reference "ECR" instead of "ECS" for Docker-based recipes
- Catch AmazonServiceException on making calls to AWS services and wrap to DeployToolException
- Server mode startup code not very resilient
Features
- Add persisted project details to API and add debugger display hints for servermode clients
- Rework deployment logging to have section headers and cleanup the logging interface
- Add VPC, Subnets and Security Groups settings to Beanstalk Recipe
Build System or External Dependencies
- Version bump to 0.42
Release 0.41.4
0.41.4
Chore
- Change NuGet package name from AWS.Deploy.CLI to AWS.Deploy.Tools
- Remove banner to notify of NuGet package name change
Build System or External Dependencies
- Version bump to 0.41
Release 0.40.18
0.40.18
Bug Fixes
- CDK not cleaning up resources after bootstrap failure
- Change Elastic Beanstalk ApplicationIAMRole service principal to ec2.amazonaws.com
- Prevent non CDK projects from being displayed as an option when creating deployment projects
- Add missing Type attribute to option setting in AppRunner recipe
- Ask for "Create New" even if options to select is empty
- Deployment doesn't fail even if cdk bootstrap fails
- Name generation reverses suffixed digits and fails over 100
- Remove --project-path argument from list-deployments command
- Throw an error when using non-existent profile names with commands
- Users can create a new stack with existing stack name
Chore
- Add banner to notify of NuGet package name change
- Enable semgrep
- Set up documentation CI/CD process
Features
- Add TypeHintData to GetConfigSettings response in Server Mode
- Add service IAM role to Elastic Beanstalk deployment configuration
- Use CDK Diff to perform server mode integ tests
Build System or External Dependencies
- Version bump to 0.40