Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

L2 Constructs for AWS MediaConvert #635

Open
1 of 11 tasks
PavanRangudu opened this issue Aug 22, 2024 · 0 comments
Open
1 of 11 tasks

L2 Constructs for AWS MediaConvert #635

PavanRangudu opened this issue Aug 22, 2024 · 0 comments
Labels
status/proposed Newly proposed RFC

Comments

@PavanRangudu
Copy link

PavanRangudu commented Aug 22, 2024

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

Role User
Proposed by @PavanRangudu
Author(s) @PavanRangudu
API Bar Raiser @alias
Stakeholders @alias, @alias, @alias

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/proposed Newly proposed RFC
Projects
None yet
Development

No branches or pull requests

1 participant