-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Personalize: Wrong attribute created in cloudformation (Python) #29411
Comments
The dataSource is type
Let me know if it works for you. |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Hello @pahud, Thanks for the info, I confirm that using a Json it works. Thanks. |
Yeah if you are using CDK in Python. Make sure to check the CDK API reference, if the prop type is |
|
Describe the bug
While creating a dataset job import for a personalize dataset with Python and cdk 2.130 the resulted cloudformation has a wrong attribute and so the deploy fails.
The correct attribute in cloudformation should be DataLocation : https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-personalize-dataset-datasource.html
Expected Behavior
This is the expected cloudformation
Current Behavior
This is the output of the cloudformation in cdk.out
Reproduction Steps
create a dataset and its importjob:
personalize.CfnDataset(
self,
dataset_name,
name=my_dataset,
dataset_type=ITEMS,
dataset_group_arn=dataset_group_arn,
schema_arn=schema_arn,
dataset_import_job=personalize.CfnDataset.DatasetImportJobProperty(
job_name=my-import-job",
role_arn=self._personalize_role.role_arn,
data_source=personalize.CfnDataset.DataSourceProperty(
data_location="s3://mybucket/mypath/items.csv",
),
)
)
Just do a synth anche check the datalocation
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.130
Framework Version
No response
Node.js Version
v18.19.1
OS
Debian 12
Language
Python
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: