awslabs / awslabs/aiops-modules
[BUG] @cdklabs/generative-ai-cdk-constructs v0.1.312 Breaking Change: Migrate to Namespaced Imports
- Dominant language
- Python
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Version 0.1.312 introduced an undocumented breaking change where SageMaker deployment constructs moved from barrel exports to namespaced exports.
Breaking Change:
// v0.1.311 and earlier (barrel exports)
export * from './patterns/gen-ai/aws-model-deployment-sagemaker';
// v0.1.312+ (namespaced exports)
export * as sagemaker_deployment from './patterns/gen-ai/aws-model-deployment-sagemaker';
Affected Modules
│ sagemaker-jumpstart-fm-endpoint │ 0.1.311 │ Migrate imports, unpin │
│ sagemaker-hugging-face-endpoint │ 0.1.74 │ Migrate imports, upgrade │
Migration Required
Update imports from direct to namespaced:
// Before
import { JumpStartModel, SageMakerInstanceType, JumpStartSageMakerEndpoint } from "@cdklabs/generative-ai-cdk-constructs";
// After
import { sagemaker_deployment } from "@cdklabs/generative-ai-cdk-constructs";
const { JumpStartModel, SageMakerInstanceType, JumpStartSageMakerEndpoint } = sagemaker_deployment;
Contributor guide
Research direction
Locate the import and dependency references for sagemaker-jumpstart-fm-endpoint and sagemaker-hugging-face-endpoint in this repository. Read how those modules consume @cdklabs/generative-ai-cdk-constructs, then compare their versions with the namespaced-import migration described here; done means the affected modules use the new namespace and the required upgrades or unpinning are reflected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100