Skip to content

Add ability to add features to existing feature groups in Sagemaker #26809

Open
@aShevc

Description

@aShevc

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

Currently when one adds new feature to the existing Sagemaker feature group, it forces the destruction of resource. However, since FeatureAdditions functionality has been introduced to the UpdateFeatureGroup API call, this must not be the case.

New or Affected Resource(s)

  • aws_sagemaker_feature_group

Potential Terraform Example

resource "aws_sagemaker_feature_group" "feature_group" {
  feature_group_name                   = "some name"
// ...rest of the configuration and features

// the feature definition below is the new feature in he feature group
    feature_definition {
      feature_name = "example_add"
      feature_type  = string
    }
}

Expected Behavior

When adding a feature to feature group, the feature group should be updated with the new feature.

Actual Behavior

Executing Terraform plan gives the following:

  # aws_sagemaker_feature_group.feature_group[0] must be replaced
-/+ resource "aws_sagemaker_feature_group" "feature_group" {

      + feature_definition { # forces replacement
          + feature_name = "example_add"
          + feature_type = "String"
        }
...

    }

Plan: 1 to add, 0 to change, 1 to destroy.

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequests to existing resources that expand the functionality or scope.service/sagemakerIssues and PRs that pertain to the sagemaker service.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions