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.

Sign up for GitHub

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

Jump to bottom

RFC | No Code Synthesis #1266

Closed
4 of 11 tasks
vinayak-kukreja opened this issue Mar 31, 2023 · 1 comment · May be fixed by #1221
Closed
4 of 11 tasks

RFC | No Code Synthesis #1266

vinayak-kukreja opened this issue Mar 31, 2023 · 1 comment · May be fixed by #1221
Assignees
@vinayak-kukreja
Labels
closed-for-staleness Issue/PR was closed due to staleness rfc/proposed RFC proposed

Comments

@vinayak-kukreja
Copy link
Contributor

Description

Current mechanism adds churn for user when synthesizing manifests for a single construct of a cdk8s library. The user would currently:

  1. Setup a cdk8s app locally.
  2. Install the library and other dependencies.
  3. Initialize the construct within the app.
  4. Compile code, if required by the programming language they are using.
  5. Run cdk8s synth to synthesize manifests.

This seems like a lot of work for just initializing a single construct. This RFC proposes adding functionality to synthesize a single construct from a cdk8s library present on package registries like NPM, PYPI.
The users would not need to setup any code locally. They would just need to mention the library url and pass in inputs for the construct to cdk8s synth command.

Roles

Role User
Proposed by @vinayak-kukreja
Author(s) @vinayak-kukreja
API Bar Raiser @iliapolo
Stakeholders @cdk8s-team/cdk8s-team

See RFC Process for details

Workflow

  • Tracking issue created (label: rfc/proposed)
  • API bar raiser assigned (ping us at #cdk8s if needed)
  • Kick off meeting
  • RFC pull request submitted (label: rfc/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label rfc/api-approved applied to pull request)
  • Final comments period (label: rfc/final-comments-period)
  • Approved and merged (label: rfc/approved)
  • Execution plan submitted (label: rfc/planning)
  • Plan approved and merged (label: rfc/implementing)
  • Implementation complete (label: rfc/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.
@vinayak-kukreja vinayak-kukreja added the rfc/proposed RFC proposed label Mar 31, 2023
@vinayak-kukreja vinayak-kukreja self-assigned this Mar 31, 2023
@iliapolo iliapolo mentioned this issue Apr 6, 2023
Open
@udaypant udaypant linked a pull request May 24, 2023 that will close this issue
chore(rfc): no code synthesis #1221
Open
@github-actions GitHub Actions
Copy link
Contributor

This issue has not received any attention in 1 year and will be closed soon. If you want to keep it open, please leave a comment below @mentioning a maintainer.

@github-actions github-actions bot added the closing-soon Issue/PR will be closing soon if no response is provided label Mar 30, 2024
@github-actions github-actions bot added closed-for-staleness Issue/PR was closed due to staleness and removed closing-soon Issue/PR will be closing soon if no response is provided labels Apr 6, 2024
@github-actions github-actions bot closed this as completed Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinayak-kukreja vinayak-kukreja

Labels
closed-for-staleness Issue/PR was closed due to staleness rfc/proposed RFC proposed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(rfc): no code synthesis cdk8s-team/cdk8s
1 participant
@vinayak-kukreja