Skip to content

fix: optional task role name in Fargate run command#3469

Merged
hassy merged 3 commits intoartilleryio:mainfrom
aryasaatvik:fargate-role-name
Feb 6, 2025
Merged

fix: optional task role name in Fargate run command#3469
hassy merged 3 commits intoartilleryio:mainfrom
aryasaatvik:fargate-role-name

Conversation

@aryasaatvik
Copy link
Contributor

@aryasaatvik aryasaatvik commented Feb 5, 2025

resolved #3470

Allow specifying a custom task role name when running Artillery on Fargate, with a fallback to the default worker role. This provides more flexibility in IAM role configuration during Fargate test runs.

Description

currently there isn't a way to pass a custom role name for tasks to assume. In PlatformECS.init it always looks for the default role name. this fixes it by passing the task-role-name flag to PlatformECS

Pre-merge checklist

This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.

  • Does this require an update to the docs?
  • Does this require a changelog entry?

Allow specifying a custom task role name when running Artillery on Fargate, with a fallback to the default worker role. This provides more flexibility in IAM role configuration during Fargate test runs.
@CLAassistant
Copy link

CLAassistant commented Feb 5, 2025

CLA assistant check
All committers have signed the CLA.

Update IAM resource creation to pass task role name as a parameter, removing the hardcoded constant and improving flexibility in role management.
@hassy
Copy link
Member

hassy commented Feb 5, 2025

thanks @aryasaatvik, kicking off e2e tests on AWS Fargate

@hassy hassy merged commit b9f8a44 into artilleryio:main Feb 6, 2025
26 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Artillery attempts to create default IAM role even when custom task role is specified via --task-role-name

3 participants