- Improved documentation around starting new projects.
- The Quickstart script now supports Pulumi Cloud and private cloud hosts.
- Fixed CI bugs where the CI user wasn't able to read details about load balancers and target gropus while deploying Fargate images.
- Under the hood, refactored a custom "Flattenable" type that represents the various types and collections we support
when auto-identifying resources in a
ThunderbirdPulumiProject
. This should be completely transparent to users. - Fixed a bug where one single security group with a combined set of rules would be applied to both a load balancer
and its container targets in a
FargateClusterWithLogging
. This is not secure, as it is permissive in each case of traffic not intended to reach the target. With this release, we support defining these groups separately.
- Can now declare recovery period for Secrets Manager Secrets built by the
RdsDatabaseGroup
class. ThunderbirdPulumiProject
s now detect resources "hidden" by output resolution through theflatten
function. This may result in some new monitors being created in your stack.- Top level
ThunderbirdPulumiProject
resource namespace pollution problem is solved by optionalexclude_from_project
parameter. - Remove some redundancy in naming some CI-related IAM resources.
- Remove Insegel theme from docs builds, relying on Furo for its dark/light modes and respect for user preference.
- Add several high priority alarms through EC2 and CloudFront.
- Allow users to set the function associations for default behaviors in a CloudFront distribution.
- Fix a bug where dimensions for some CloudWatch alarms did not get set correctly, resuling in "Insufficient Data" all the time.
- Verification of Pulumi resource dependencies throughout the codebase. This repairs the dependency tree and makes destroys and environment rebuilds smooth.
- Lock the AWS provider to a specific version to avoid errors when CI automation runs pulumi commands with
--target
. - Add an
environment
tag to all AWS resources for cost tracking purposes. - Build the initial patterns to use for developing project-at-once monitoring solutions.
- Fixed bugs in the new CI features of v0.0.5 where certain permissions were lacking in some of the IAM polices.
- Added documentation of the CI module.
- Added feature to
CloudFrontS3Service
s where S3 buckets can be forcibly destroyed, even if they contain objects. - The
secrets
module has been refactored in two ways:- The
SecretsManagerSecrets
class now passes all extra keyword arguments into theSecret
resource, allowing for configuration of other inputs of that resource. - The
PulumiSecretsManager
class no longer manages its ownSecret
andSecretVersion
resources, relying instead on theSecretsManagerSecrets
class to better organize things. **This particular change may present challenges at the time your Pulumi code is upgraded to v0.0.5, as it will cause a recreation of all secrets managed through this module. This will result in new ARNs which you will have to update anywhere they are used.
- The
- These features both serve to make destroying and rebuilding stacks less painful.
- Resolved issues related to S3 bucket permissions which were preventing clean environment builds from scratch (Issue #21).
- Resolved a bug where some execution environments were not able to determine the name of the user running the Pulumi command (Issue #24).
- Redesigned the internal patterns by which resources are tracked; properly divided the concept of resource tracking from that of Pulumi outputs (Issue #20).
- Added some IAM resources to help manage the capabilities of CI robots (Issue #26).
- Overhauled documentation.
- Only docstrings have changed with this version.
- No actual code changes have been made.
- Added
CloudFrontS3Service
pattern for serving static content over a CDN.
- Initial commit supporting basic infrastructure required to run a Fargate service on private network space.