You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create L2 Constructs for AWS MediaConvert service. Currently, only the autogenerated Cfn Constructs(L1) are supported which involves specifying detailed JSON structures as input that is cumbersome and error-prone. Developers need to understand the exact format and structure required by MediaConvert, as well as how to translate that into CDK code. This process could be greatly simplified with the support of L2 constructs.
Existing tracking issue for prioritizing high-level constructs for MediaConvert: aws/aws-cdk#6852 (Open)
API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
Kick off meeting
RFC pull request submitted (label: status/review)
Community reach out (via Slack and/or Twitter)
API signed-off (label status/api-approved applied to pull request)
Final comments period (label: status/final-comments-period)
Approved and merged (label: status/approved)
Execution plan submitted (label: status/planning)
Plan approved and merged (label: status/implementing)
Implementation complete (label: status/done)
Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.
The text was updated successfully, but these errors were encountered:
Description
Create L2 Constructs for AWS MediaConvert service. Currently, only the autogenerated Cfn Constructs(L1) are supported which involves specifying detailed JSON structures as input that is cumbersome and error-prone. Developers need to understand the exact format and structure required by MediaConvert, as well as how to translate that into CDK code. This process could be greatly simplified with the support of L2 constructs.
Existing tracking issue for prioritizing high-level constructs for MediaConvert:
aws/aws-cdk#6852 (Open)
RFC PR: #639
Roles
Workflow
status/proposed
)status/review
)status/api-approved
applied to pull request)status/final-comments-period
)status/approved
)status/planning
)status/implementing
)status/done
)The text was updated successfully, but these errors were encountered: