7cb9ce2663
This change refactors the existing property verification logic for the AWS provider to use the new checking capabilities. Beyond just checking for required properties, there isn't much here yet. There is a single check for security group description length that goes beyond this, mostly for illustration purposes. This is part of pulumi/coconut#115, although there is clearly more to do here for something sufficiently snazzy and demoable. |
||
|---|---|---|
| .. | ||
| aws | ||
| cocojs | ||
| coconut | ||
| coconutx | ||
| README.md | ||
coconut/lib
This directory contains the various libraries (Nuts) that Coconut programs may depend upon.
The Coconut standard library underneath coconut/ is special in that every program will ultimately use it directly or
indirectly to create resources.
Note that these are written in the Coconut subsets of the languages and therefore cannot perform I/O, etc.
Eventually these packages will be published like any other NPM package. For now, they are consumed only in a development capacity, and so there are some manual steps required to prepare a development workspace.
For each library <lib> you wish to use, in dependency order:
cd <lib>yarn install- For each dependency
<dep>:yarn link dep
yarn buildyarn link
And then from within each Nut's directory, <lib>, that will consume said libraries:
yarn link <lib>
For example, let's say we want to use the standard library and the AWS library from another Nut, /dev/mypackage:
- First,
cd $GOPATH/src/github.com/pulumi/coconut/lib/coconut:yarn installyarn buildyarn link
- Next,
cd $GOPATH/src/github.com/pulumi/coconut/lib:yarn installyarn link @coconut/coconutyarn buildyarn link
- Finally,
cd /dev/mypackage:yarn link @coconut/coconutyarn link @coconut/aws
- Now we are ready to go working on
mypackage, and the two Nut references will be resolved correctly.