Skip to content

Conversation

@alexalbu001
Copy link

@alexalbu001 alexalbu001 commented Dec 12, 2025

Updates POWERTOOLS_SERVICE_NAME to use the prefix variable instead of hardcoded values in pool, ami-housekeeper, scale-down, scale-up, webhook and dispatcher Lambda functions.

Why

  • function names already include prefix, POWERTOOLS_SERVICE_NAME should too

@alexalbu001 alexalbu001 requested a review from a team as a code owner December 12, 2025 15:06
@alexalbu001 alexalbu001 changed the title update POWERTOOLS_SERVICE_NAME env var to use the prefix var feat: use prefix variable for POWERTOOLS_SERVICE_NAME in Lambda functions Dec 12, 2025
@alexalbu001 alexalbu001 force-pushed the feat/use-prefix-for-powertools-service-name branch from 835b1a0 to d82d6f7 Compare December 12, 2025 15:09
Copy link
Member

@npalm npalm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexalbu001 thx, can you also fix the following places in code as well.

  • modules/runners/pool/main.tf
  • modules/runners/ssm-housekeeper.tf

PR looks good.

@alexalbu001 alexalbu001 force-pushed the feat/use-prefix-for-powertools-service-name branch from ffa0ba0 to b02518c Compare December 14, 2025 21:34
@alexalbu001 alexalbu001 requested a review from npalm December 14, 2025 21:42
@alexalbu001
Copy link
Author

@npalm should be good now

@npalm
Copy link
Member

npalm commented Dec 18, 2025

Sorry for the late catch, but why do you think the service name should include the prefix as well. The initial idea was to set only the name of the service, since it is in context of the lambda the prefix is part of that.

@alexalbu001
Copy link
Author

I understand the design philosophy of keeping the service name as a logical identifier separate from the deployment context, however, I see a few benefits to including the prefix:

  • Consistency with function names: The Lambda function names already include the prefix (${var.prefix}-scale-up). Having POWERTOOLS_SERVICE_NAME match the function name creates consistency between what users see in the AWS console and what appears in their observability tools.
  • Current behaviour: The existing hardcoded values already include "runners-" prefix (e.g., "runners-scale-up"), so this change just makes that pattern configurable rather than changing the philosophy

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.

2 participants