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

AWS Amplify Console - Add L2 Construct #3207

Closed
1 of 5 tasks
simalexan opened this issue Jul 4, 2019 · 6 comments
Closed
1 of 5 tasks

AWS Amplify Console - Add L2 Construct #3207

simalexan opened this issue Jul 4, 2019 · 6 comments
Assignees
Labels
@aws-cdk/aws-amplify Related to AWS Amplify effort/large Large work item – several weeks of effort feature-request A feature should be added or improved. in-progress This issue is being actively worked on.

Comments

@simalexan
Copy link

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.

  • I'm submitting a ...

    • 🪲 bug report
    • 🚀 feature request
    • 📚 construct library gap
    • ☎️ security issue or vulnerability => Please see policy
    • ❓ support request => Please see note at the top of this template.
  • What is the current behavior?
    If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce

  • What is the expected behavior (or behavior of feature suggested)?
    Since AWS Amplify Console is now within CDK as an L1 Construct it would be great if this can also be made available within CDK as an L2 Construct and I'd like to contribute to it, as its a relatively small case.

  • What is the motivation / use case for changing the behavior or adding this feature?
    Enable AWS customers to use a nicer and more convenient AWS CDK L2 Construct API

  • Please tell us about your environment:

    • CDK CLI Version: 0.37.0
    • Module Version: 0.37.0
    • OS: all
    • Language: all
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)

I've started today, please let me know if someone would like to add their contribution as well. I shall ping also @sthulb for assistance in this.

@simalexan simalexan added the needs-triage This issue or PR still needs to be triaged. label Jul 4, 2019
@sthulb
Copy link
Contributor

sthulb commented Jul 4, 2019

@simalexan I’ve already started this. I’ve got the app resource mostly done. :)

@sthulb
Copy link
Contributor

sthulb commented Jul 4, 2019

Hey @swaminator we’re tracking the work here.

@simalexan
Copy link
Author

@sthulb great can you share the repo pls? :) I've got the starting points of all three, and willing to add.

Sorry, I didn't see the AWS CDK issue for this per the Contribution guideline, so unfortunate :/

@sthulb
Copy link
Contributor

sthulb commented Jul 4, 2019

I’ll push it tomorrow. I’ll ping you on slack tomorrow to run through it

@simalexan
Copy link
Author

Alrighty then! Glad I pinged you here!

@eladb eladb assigned eladb and shivlaks and unassigned eladb Aug 12, 2019
@SomayaB SomayaB added the feature-request A feature should be added or improved. label Oct 10, 2019
@NGL321 NGL321 added @aws-cdk/aws-amplify Related to AWS Amplify in-progress This issue is being actively worked on. and removed needs-triage This issue or PR still needs to be triaged. labels Oct 10, 2019
@NGL321 NGL321 self-assigned this Oct 10, 2019
@shivlaks shivlaks added the effort/large Large work item – several weeks of effort label Feb 6, 2020
@MrArnoldPalmer
Copy link
Contributor

Closed via #5177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-amplify Related to AWS Amplify effort/large Large work item – several weeks of effort feature-request A feature should be added or improved. in-progress This issue is being actively worked on.
Projects
None yet
Development

No branches or pull requests

7 participants