Skip to content

Comments

feat(logging): add log_class parameter to runner log files configuration#5036

Open
Brend-Smits wants to merge 2 commits intomainfrom
feat/specify-log-classes
Open

feat(logging): add log_class parameter to runner log files configuration#5036
Brend-Smits wants to merge 2 commits intomainfrom
feat/specify-log-classes

Conversation

@Brend-Smits
Copy link
Contributor

This pull request updates the logging configuration by introducing support for the log_class property, allowing log groups to be created with either the STANDARD or INFREQUENT_ACCESS class. The change is applied throughout the configuration to ensure log groups and log files can specify their class, defaulting to STANDARD if not set.

Logging configuration enhancements:

  • Added a log_class property (defaulting to "STANDARD") to the runner_log_files and multi_runner_config variables in variables.tf, modules/runners/variables.tf, and modules/multi-runner/variables.tf to allow specifying the log group class. [1] [2] [3]
  • Updated the local log file definitions in modules/runners/logging.tf to include the log_class property for each log file, defaulting to "STANDARD".
  • Modified the CloudWatch log group resource in modules/runners/logging.tf to use the specified log_class when creating log groups, and refactored the logic to group log files by both name and class.

Documentation improvements:

  • Enhanced the description of the runner_log_files variable to document the new log_class property and its valid values.

@Brend-Smits Brend-Smits requested review from a team as code owners February 16, 2026 10:44
@github-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant