Skip to content
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

Add platform_identifier support to r/aws_sagemaker_notebook_instance #20706

Closed
lastlee opened this issue Aug 27, 2021 · 3 comments · Fixed by #20711
Closed

Add platform_identifier support to r/aws_sagemaker_notebook_instance #20706

lastlee opened this issue Aug 27, 2021 · 3 comments · Fixed by #20711
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/sagemaker Issues and PRs that pertain to the sagemaker service.
Milestone

Comments

@lastlee
Copy link
Contributor

lastlee commented Aug 27, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

AWS recently added support for PlatformIdentifier: the ability to specify AL1 or AL2 Sagemaker platforms: https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_DescribeNotebookInstance.html#sagemaker-DescribeNotebookInstance-response-PlatformIdentifier

One caveat: aws-sdk-go supports PlatformIdentifier but does not have supporting components for validation

New or Affected Resource(s)

  • aws_sagemaker_notebook_instance

Potential Terraform Configuration

resource "aws_sagemaker_notebook_instance" "test" {
  name                = "test-notebook-al2"
  role_arn            = aws_iam_role.test.arn
  instance_type       = "ml.t2.medium"
  platform_identifier = "notebook-al2-v1"
}

References

@lastlee lastlee added the enhancement Requests to existing resources that expand the functionality or scope. label Aug 27, 2021
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/sagemaker Issues and PRs that pertain to the sagemaker service. labels Aug 27, 2021
@anGie44 anGie44 removed the needs-triage Waiting for first response or review from a maintainer. label Aug 27, 2021
@anGie44
Copy link
Contributor

anGie44 commented Aug 27, 2021

@lastlee , thanks for raising this issue! If you're referring to plan-time validation components, within the resource code, you can use a regex instead within the platform_identifier field e.g.

"platform_identifier": {
  Type: schema.TypeString,
  ...,
  ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(notebook-al1-v1|notebook-al2-v1)$`), ""),
}

@github-actions
Copy link

github-actions bot commented Sep 2, 2021

This functionality has been released in v3.57.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/sagemaker Issues and PRs that pertain to the sagemaker service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants