You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: The value sagemaker_pipeline_parameters.value.pipeline_parameter should not be enclosed in brackets to allow multiple parameters.
✋ I have searched the open/closed issues and my issue is not listed.
Versions
Module version [Required]: 3.13.0
Terraform version:
1.9.6
Provider version(s):
AWS Provider Version: 5.79.0
Reproduction Code [Required]
schedules=[
{
name ="test"
schedule_expression ="rate(1 day)"
arn ="arn:aws:sagemaker:{AWS_REGION}:{AWS_ACCOUNT_ID}:pipeline/{PIPELINE_NAME}"
role_arn ="arn:aws:iam::{AWS_ACCOUNT_ID}:role/{AWS_ROLE_NAME}"
sagemaker_pipeline_parameters = {
pipeline_parameter = [{
name ="parameter-1"
value ="value-1"
},
{
name ="parameter-2"
value ="value-1"
}]
}
}
]
Steps to reproduce the behavior:
Just create a simple schedule for the module like the above and the result plan should show the sagemaker_pipeline_parameters block empty
No
Yes
Expected behavior
Both parameters should be added
Actual behavior
Empty block for sagemaker_pipeline_parameters
The text was updated successfully, but these errors were encountered:
Description
The Terraform module contains a bug when attempting to apply a event bridge schedule with a SageMaker pipeline with parameters as target.
Issues
1. Dynamic Block Lookup Issue
The
lookup
inside the dynamic block is not using the.value
attribute Line to fixFix: Update the
lookup
to:2. Limited Parameters in Dynamic Block
With the current for_each implementation in the dynamic block, it's only possible to pass one parameter.
Fix: Update the
for_each
to:Note: The value
sagemaker_pipeline_parameters.value.pipeline_parameter
should not be enclosed in brackets to allow multiple parameters.Versions
Module version [Required]: 3.13.0
Terraform version:
1.9.6
Provider version(s):
AWS Provider Version: 5.79.0
Reproduction Code [Required]
Steps to reproduce the behavior:
Just create a simple schedule for the module like the above and the result plan should show the
sagemaker_pipeline_parameters
block emptyNo
Yes
Expected behavior
Both parameters should be added
Actual behavior
Empty block for sagemaker_pipeline_parameters
The text was updated successfully, but these errors were encountered: