When you create an aws_sagemaker_domain or aws_sagemaker_user_profile with custom_file_system_config, and once created you remove this property the resource should be properly modified and should remove this configuration.
Actual Behavior
When you create an aws_sagemaker_domain or aws_sagemaker_user_profile with custom_file_system_config, and once created you remove this property the resource keeps the configuration and every time you try to make a terraform apply or plan it appers as a resource to be changed but it never accepts the removal of this property.
Create a user with a custom_file_syste_config like:
resource "aws_sagemaker_user_profile" "this" {
user_settings {
custom_file_system_config {
efs_file_system_config {
file_system_id = var.efs_space_id
file_system_path = var.efs_space_path
}
}
}
}
It will perfectly create it. But when you modify the code to remove this property, it will be displayed as a resource to be changed in the terraform plan but this configuration will never be replace in the aws resource. And every time you try to make a terraform apply or terraform plan it will continue to be displayed as a resource to be changed.
~ user_settings {
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.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
0.14.7
AWS Provider Version
5.76.0
Affected Resource(s)
aws_sagemaker_domain aws_sagemaker_user_profile
Expected Behavior
When you create an aws_sagemaker_domain or aws_sagemaker_user_profile with custom_file_system_config, and once created you remove this property the resource should be properly modified and should remove this configuration.
Actual Behavior
When you create an aws_sagemaker_domain or aws_sagemaker_user_profile with custom_file_system_config, and once created you remove this property the resource keeps the configuration and every time you try to make a terraform apply or plan it appers as a resource to be changed but it never accepts the removal of this property.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
resource "aws_sagemaker_user_profile" "this" { user_settings { custom_file_system_config { efs_file_system_config { file_system_id = var.efs_space_id file_system_path = var.efs_space_path } } } }
Steps to Reproduce
Create a user with a custom_file_syste_config like: resource "aws_sagemaker_user_profile" "this" { user_settings { custom_file_system_config { efs_file_system_config { file_system_id = var.efs_space_id file_system_path = var.efs_space_path } } } }
It will perfectly create it. But when you modify the code to remove this property, it will be displayed as a resource to be changed in the terraform plan but this configuration will never be replace in the aws resource. And every time you try to make a terraform apply or terraform plan it will continue to be displayed as a resource to be changed. ~ user_settings {
(3 unchanged attributes hidden)
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None