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

Sagemaker Domain - Support retaining EFS File system #17349

Closed
DrFaust92 opened this issue Jan 28, 2021 · 3 comments · Fixed by #18562
Closed

Sagemaker Domain - Support retaining EFS File system #17349

DrFaust92 opened this issue Jan 28, 2021 · 3 comments · Fixed by #18562
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

@DrFaust92
Copy link
Collaborator

DrFaust92 commented Jan 28, 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

Add an argument to retain Sagemaker Domain EFS File system upon deletion. This change will revert current behaviour change introduced in #17123

New or Affected Resource(s)

  • aws_sagemaker_domain

Potential Terraform Configuration

resource "aws_sagemaker_domain" "example" {
  domain_name        = "example"
  auth_mode          = "IAM"
  vpc_id             = aws_vpc.test.id
  subnet_ids         = [aws_subnet.test.id]

  retain_policy {
    home_efs_file_system = "Delete|Retain" # Default: Retain
  }

  default_user_settings {
    execution_role = aws_iam_role.test.arn
  }
}

References

@DrFaust92 DrFaust92 added the enhancement Requests to existing resources that expand the functionality or scope. label Jan 28, 2021
@ghost ghost added the service/sagemaker Issues and PRs that pertain to the sagemaker service. label Jan 28, 2021
@bflad
Copy link
Contributor

bflad commented Jan 29, 2021

Since the DeleteDomain API models this as a structure with a string parameter, we might want to do the same. 👍

resource "aws_sagemaker_domain" "example" {
  # ... other configuration ...

  retain_policy {
    home_efs_file_system = "Delete|Retain" # Default: Retain
  }
}

Then the logic can skip adding it if the block is not declared (essentially reverting it back to the default behavior):

func resourceAwsSagemakerDomainDelete(d *schema.ResourceData, meta interface{}) error {
	conn := meta.(*AWSClient).sagemakerconn

	input := &sagemaker.DeleteDomainInput{
		DomainId: aws.String(d.Id()),
	}

	if v, ok := d.GetOk("retention_policy"); ok && len(v.([]interface{})) > 0 && v.([]interface{})[0] != nil {
		input.RetentionPolicy = expandSagemakerRetentionPolicy(v.([]interface{}))
	}

To prevent confusion we have seen in other resources with destroy-time configuration, it would also be good to include additional cues in the documentation that this configuration must be applied in the Terraform state before the resource destroy operation.

@github-actions
Copy link

This functionality has been released in v3.50.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 Aug 15, 2021
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