-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[stepfunctions-tasks] SageMakerCreateEndpointConfig cannot use JSONPath.stringAt for ec2.InstanceType #11605
Labels
@aws-cdk/aws-stepfunctions-tasks
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
Comments
ntroutman
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
Nov 20, 2020
SomayaB
changed the title
[aws-stepfunction-tasks] SageMakerCreateEndpointConfig cannot use JSONPath.stringAt for ec2.InstanceType
[stepfunctions-tasks] SageMakerCreateEndpointConfig cannot use JSONPath.stringAt for ec2.InstanceType
Nov 23, 2020
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-stepfunctions-tasks
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
CDK throws an error when passing
ec2.InstanceType(JsonPath.stringAt(...))
when defining the instance type used for tasks.SageMakerCreateEndpointConfig.Reproduction Steps
What did you expect to happen?
That I could refer to the step-functions state using JsonPath to configure the instance type used in an Endpoint Configuration.
What actually happened?
CDK threw the following error:
Environment
Other
It's pretty clear from the error that the SageMaker Tasks is using TypeScript string interpolation to prefix the instance type with "ml."
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: