https://pulumi.com logo
#general
Title
# general
w

white-balloon-205

11/27/2018, 5:45 AM
This is a current limitation of
cloudaws.Service
unfortunately. It's tracked by https://github.com/pulumi/pulumi-cloud/issues/91. This particular one is likely quite easy to add. If you are interested in submitting a PR, we'd be happy to accept it - else I'll see if we can get this (and other similar low hanging fruit for container options) added soon. Note that we're also working on an API that will be more "ECS-native" but still offer the high-level benefits of
cloudaws.Service
- while not having these sharp edges. I'll reach out with some more details on this a little later this week - as a user of
cloudaws.Service
- we'd love your early feedback on this and whether it would address your needs.
f

full-dress-10026

11/27/2018, 6:37 AM
Yes I may take a stab at a PR tomorrow as we need this flag asap. I would definitely be interested and happy to provide feedback on the ECS native API.
@white-balloon-205 How do I get dependencies installed for pulumi-cloud to get started on a PR? Just running
npm install
in the
aws
directory does not work due to "Invalid version: "${VERSION}"".
Maybe there's a doc on dev environment setup?
w

white-balloon-205

11/27/2018, 5:14 PM
Run
make ensure
and then
make
in the root of the project. That will set up
yarn
links for all the packages built in this repo. From your test program, you can then run
yarn link @pulumi/cloud
and
yarn link @pulumi/cloud-aws
. I believe that currently to work with the dev process you do need to use
yarn
instead of
npm
(just due to the linking hooked up as part of the dev build process).
I thought we had a
CONTRIBUTING.md
in that repo - but looks like we don't yet - I'll open an issue to track that.
f

full-dress-10026

11/27/2018, 5:18 PM
I see there's a #contribute channel. I'll move the conversation there.