What autobase-tech/autobase shipped
Written by FoxPlug from public releases; not affiliated with Autobase. An automatic summary of the public release, pull request and commit data of github.com/autobase-tech/autobase. Autobase did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- Azure VM pricing updated with Dsv6 and Esv6 series including larger 128 and 192 vCPU options, while B-series instances removed due to availability issues. Pull request #1718
- Console now automatically selects provider-specific default cloud regions when creating new clusters instead of requiring manual selection. Pull request #1719
- AWS EC2 instances can now be created in non-default subnets using the new
vpc_subnet_idoption. Pull request #1715 - AWS EC2 volumes now support
volume_nameandsystem_volume_namevariables for better identification. Pull request #1716 - Fixed duplicate host entries in in-memory inventory generation during resizefs operations. Pull request #1717
Why it matters
Azure pricing now reflects current VM availability and larger instance options. AWS deployments gain flexibility for subnet selection and volume naming. Cluster creation becomes faster with automatic region defaults.
Changelog entry
- Azure: Updated VM pricing with Dsv6 and Esv6 series (up to 192 vCPU), removed B-series instances Pull request #1718
- Console: Automatic default region selection for new clusters based on provider preferences Pull request #1719
- AWS: Added
vpc_subnet_idoption for EC2 instance creation in non-default subnets Pull request #1715 - AWS: Added
volume_nameandsystem_volume_namevariables for EC2 volumes Pull request #1716 - Fixed: Duplicate hosts in in-memory inventory during resizefs operations Pull request #1717
This week: Azure pricing refresh with Dsv6/Esv6 series, automatic cloud region selection for new clusters, AWS subnet and volume naming improvements, and inventory deduplication fixes.
This week's updates improve cloud infrastructure flexibility. Azure VM pricing now includes the latest Dsv6 and Esv6 series with larger instance sizes while removing unavailable B-series options. The console automatically selects optimal cloud regions when creating clusters. AWS deployments gain the ability to specify subnets and name volumes. Fixed duplicate host entries in inventory generation.
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_generationset todisabledby default,on_createfor new users, oralwaysfor rotation. Pull request #1712 - External secrets provider support added through a new
vitabaks.autobase.secretsrole 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_idsvariable. Pull request #1707 - EBS encryption now enabled by default with
aws_ebs_encryptedand optionalaws_ebs_kms_key_idfor 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_instancenow applies ownership tags atomically during creation. Pull request #1700 - PostgreSQL users role fixed by adding missing
login_dbparameter to theGrant roles to userstask. Pull request #1705 - Firewall hostvars lookup corrected to use
inventory_hostnameinstead ofbind_addressfor 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_createfor new users, always for rotation) Pull request #1712 - External secrets provider support added for AWS Secrets Manager through new
vitabaks.autobase.secretsrole Pull request #1711 - AWS: Multiple Security Groups support via
aws_security_group_idsvariable combining user-defined and role-managed groups Pull request #1707 - AWS: EBS encryption enabled by default with
aws_ebs_encryptedand optionalaws_ebs_kms_key_idfor KMS support Pull request #1706 - Per-replica cloud load balancer controls added:
cloud_load_balancer_replica,cloud_load_balancer_replica_sync, andcloud_load_balancer_replica_asyncPull 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_instancePull request #1700 - PostgreSQL users: Added missing
login_dbparameter to role grant task Pull request #1705 - Firewall configuration: Fixed hostvars lookup to use
inventory_hostnameinstead ofbind_addressPull request #1710 - pgBackRest: Added
diff: falseto prevent sensitive data logging in diff mode Pull request #1709 - pgBackRest: Added
no_logto prevent sensitive configuration details logging Pull request #1708 - Upgrade: Fixed doubled log path in
recovery_targetLSN 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.