$40976 Fix validation for SageMaker App Image Config: API rejects valid UID/GID pairs defined in provider schema #41112
+131
−124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes
This PR fixes the validation for the
aws_sagemaker_app_image_config
resource's FileSystemConfig by updating the allowed values fordefault_uid
anddefault_gid
to match AWS API requirements. Currently, the provider schema allows values (0) that the AWS API rejects.Fixes #40976
Output from Acceptance Testing
Additional Details
The AWS SageMaker API only supports specific values for FileSystemConfig:
default_uid
: 1000default_gid
: 100However, the current provider schema allows values (0) that the API rejects with:
This PR updates the schema validation to only allow the supported values, providing better user experience by failing fast during plan phase rather than during apply.