Full Changelog: v0.1.0...v1.0.0
Release Description for v1.0.0
Enhancements:
-
Support for Multiple Clusters: The new release introduces the capability to handle logs from multiple clusters. Users have now the option to aggregate logs from all clusters under a single naming scheme "all_clusters" or specify individual cluster names.
-
Dynamic Resource Creation: With the introduction of the
for_each
directive, resources like the logging bucket, random suffix, logging sink, and IAM bindings are now dynamically created based on the number of clusters specified. This ensures scalability and flexibility in handling logs from multiple clusters. -
Customizable Retention Days: The retention period for logs stored in the bucket can now be customized using the
var.retention_days
variable, providing users with more control over their log retention policies. -
Refined Filtering: The default filter has been streamlined to focus on stderr and stdout logs from the source project. Additionally, users can now provide a custom log filter using the
var.custom_log_filter
variable, offering more granularity in log filtering. -
Code Organization: The code has been restructured for better readability, with clear demarcations for local variables and resources.
Deprecations:
-
The
var.log_filter_custom
variable has been deprecated in favor of the more descriptivevar.custom_log_filter
. -
The
var.cluster_name
variable has been replaced byvar.cluster_names
to support multiple clusters.
Notes:
Existing users should review their configurations, especially if they were using the var.log_filter_custom
or var.cluster_name
variables, and update them accordingly to ensure compatibility with v1.0.0.