What autobase-tech/autobase shipped
Generated by FoxPlug from public activity — not affiliated with Autobase.
Week of September 14, 2026
What shipped
- Autobase 2.11.0 released, marking a milestone for full PostgreSQL lifecycle management. Release
- PostgreSQL users role now supports configurable password generation with `postgresql_users_password_generation` set to `disabled` by default, `on_create` for new users, or `always` for rotation. Pull request #1712
- External secrets provider support added through a new `vitabaks.autobase.secrets` role for exporting and storing secrets in AWS Secrets Manager. Pull request #1711
- Per-replica cloud load balancer controls added with independent settings across all supported cloud providers. Pull request #1695
- AWS support extended to attach multiple Security Groups to EC2 instances and Spot instances via `aws_security_group_ids` variable. Pull request #1707
- EBS encryption now enabled by default with `aws_ebs_encrypted` and optional `aws_ebs_kms_key_id` for KMS key support. Pull request #1706
- Post-creation resource tagging removed for Azure, GCP, DigitalOcean, and Hetzner Cloud by moving ownership tags to provider module creation. Pull request #1701
- AWS post-creation EC2 tagging tasks removed as `amazon.aws.ec2_instance` now applies ownership tags atomically during creation. Pull request #1700
- PostgreSQL users role fixed by adding missing `login_db` parameter to the `Grant roles to users` task. Pull request #1705
- Firewall hostvars lookup corrected to use `inventory_hostname` instead of `bind_address` for consistency across the collection. Pull request #1710
Why it matters
Version 2.11 represents a major step forward for managing PostgreSQL clusters end-to-end. This week's updates add critical security features like external secrets integration and EBS encryption, improve password management flexibility, and fix configuration issues that affected role assignment and firewall setup. Cloud providers also see efficiency gains from eliminating redundant post-creation tagging.
Changelog entry
- PostgreSQL users password generation now configurable via `postgresql_users_password_generation` (disabled by default, on_create for new users, always for rotation) Pull request #1712
- External secrets provider support added for AWS Secrets Manager through new `vitabaks.autobase.secrets` role Pull request #1711
- AWS: Multiple Security Groups support via `aws_security_group_ids` variable combining user-defined and role-managed groups Pull request #1707
- AWS: EBS encryption enabled by default with `aws_ebs_encrypted` and optional `aws_ebs_kms_key_id` for KMS support Pull request #1706
- Per-replica cloud load balancer controls added: `cloud_load_balancer_replica`, `cloud_load_balancer_replica_sync`, and `cloud_load_balancer_replica_async` Pull request #1695
- Post-creation tagging removed for Azure, GCP, DigitalOcean, and Hetzner Cloud; ownership tags now passed at resource creation Pull request #1701
- AWS post-creation EC2 tagging removed; ownership tags applied atomically by `amazon.aws.ec2_instance` Pull request #1700
- PostgreSQL users: Added missing `login_db` parameter to role grant task Pull request #1705
- Firewall configuration: Fixed hostvars lookup to use `inventory_hostname` instead of bind_address Pull request #1710
- pgBackRest: Added `diff: false` to prevent sensitive data logging in diff mode Pull request #1709
- pgBackRest: Added `no_log` to prevent sensitive configuration details logging Pull request #1708
- Upgrade: Fixed doubled log path in recovery_target LSN check during blue-green major-version upgrade Pull request #1694
Autobase 2.11 ships with AWS Secrets Manager integration, configurable PostgreSQL password generation, EBS encryption by default, and multi-security group support. Plus fixes for replica load balancing controls.
Autobase 2.11 is here. This release brings external secrets management through AWS Secrets Manager, flexible password generation for PostgreSQL users, EBS encryption enabled by default, and independent replica load balancer controls across all cloud providers. We've also eliminated redundant post-creation tagging and fixed critical issues in role assignment and firewall configuration. Full PostgreSQL lifecycle management just got stronger.