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

[FEAT] aws-cdk support #29

Open
dbartholomae opened this issue Jun 20, 2020 · 6 comments
Open

[FEAT] aws-cdk support #29

dbartholomae opened this issue Jun 20, 2020 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@dbartholomae
Copy link

Is your feature request related to a problem? Please describe.
I've been working a bit on setting up an aws-cdk builder so I can also manage my infrastructure as code via NX.

Describe the solution you'd like
I've now found you nx-aws-cdk builder and schema and would like to avoid double work. What's the status? Do you plan on publishing to npm any time soon?

Describe alternatives you've considered
Any way I can help? Otherwise I would most likely work on this on my own, and maybe get some inspiration from your work so far.

Check which provider is affected:
[X] AWS
[] Azure
[] Google Cloud Platform

Check which framework is affected:
[] Angular
[] Nodejs
[] Serverless
[] Lambda
[X] Infrastructure as a code

@dbartholomae dbartholomae added the enhancement New feature or request label Jun 20, 2020
@wickstargazer
Copy link
Member

Hi,

I have been meaning to test it out on starting up an ec2-instance inside our company. I want to publish it asap but could not find the time to test it out properly so dint want to publish a buggy version!

Would be great if you can help out! 😄

Would you want to test out if the schematics and the runner work? and if not maybe adjust it around a little bit? I am planning to add several more schematics like ECS, S3 static websites, or more advance infra stuff like VPC, Elastic search etc into it as well.

@dbartholomae
Copy link
Author

I've played around a bit and currently aim to get it done without a separate builder by using the run-commands builder. I'm currently a bit stuck on a cwd issue: The jest builder runs tests with the main repo as the cwd, not the specific apps folder. This folder needs to contain the cdk.json file, though, and I haven't found a way yet to tell cdk synth where to find it.

@wickstargazer
Copy link
Member

@dbartholomae thats where the builder comes in. Inside it is using nx-command but wrapping it around some builders to make sure things work according to what we want and there is a magic 'waitUntilTargetparameter to help us pick what needs to be done first like thejest` command :)

@wickstargazer
Copy link
Member

@dbartholomae so, shoudl we work together to publish its first version this week? :)

@dbartholomae
Copy link
Author

Unfortunately I'm a bit swamped now :-/

@wickstargazer
Copy link
Member

Hi! our team is working through this to get our own infrastructure into nx ... it will be on the branch testing-cdk-build

Let us know if you have any input or ideas, we will be glad to help incorporate it! ...

@beamflowaccount will be the main man looking at it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants