pulumi/.gitignore

*.swp
/vendor/
**/node_modules/
**/bin
**/.vscode/
**/.vs/
coverage.cov
*.coverprofile

/.idea/
*.iml

# VSCode creates this binary when running tests in the debugger
**/debug.test

# Go tests run "in tree" and this folder will linger if they fail (the integration test framework cleans
# it up when they pass.)
**/command-output/

# By default, we don't check in yarn.lock files
**/yarn.lock
Gitignore *.swp files 2016-11-16 18:28:46 +01:00			`*.swp`
Revert "The Go vendoring saga continues" This reverts commit f939651c64409fb168911f1271de5b86840e4602. This particular saga appears to never end... 2017-08-02 02:51:38 +02:00			`/vendor/`
Add license fields to package.json. (#1656) 2018-07-25 01:10:13 +02:00			`**/node_modules/`
Add a SxS test for `@pulumi/pulumi` to help catch when we make breaking changes to core types. (#2610) 2019-03-29 20:27:42 +01:00			`**/bin`
Fix a couple of issues when projecting Protobuf and UNKNOWN in Python (#1468) * Fix a few issues with the Python language host 1. Fix an issue where the UNKNOWN sentinel was leaking into user programs 2. Fix an issue where Protobuf types were leaking into user programs In fixing this issues I also added a framework for writing tests against the Python SDK. * License headers, and adopt a more idiomatic testing pattern * Additional idiomatic Python * That's what I get for trying to be fancy (Travis CI python version is very old and does not respect this form) * CR feedback: use more comprehensions, typo fix * Break a circular dependency between resource, runtime.resource, and runtime.rpc * Don't check in .vscode * CR: sort inputs, rename global variable, add a test for CustomResource serialization * Remove accidental code duplication 2018-06-07 01:09:07 +02:00			`**/.vscode/`
Add preview .NET Core support for pulumi. (#3399) 2019-10-26 01:59:50 +02:00			`**/.vs/`
Add Go code coverage reports to nightly tests Adds a make task to generate code coverage for all Go sources. That make task re-runs the tests, and can be fairly expensive, so it is enabled only in the nightly tests for now. Part of #206. 2017-06-24 00:11:20 +02:00			`coverage.cov`
			`*.coverprofile`
Sketch a `mu build` command and its scaffolding This adds a bunch of general scaffolding and the beginning of a `build` command. The general engineering scaffolding includes: * Glide for dependency management. * A Makefile that runs govet and golint during builds. * Google's Glog library for logging. * Cobra for command line functionality. The Mu-specific scaffolding includes some packages: * mu/pkg/diag: A package for compiler-like diagnostics. It's fairly barebones at the moment, however we can embellish this over time. * mu/pkg/errors: A package containing Mu's predefined set of errors. * mu/pkg/workspace: A package containing workspace-related convenience helpers. in addition to a main entrypoint that simply wires up and invokes the CLI. From there, the mu/cmd package takes over, with the Cobra-defined CLI commands. Finally, the mu/pkg/compiler package actually implements the compiler behavior. Or, it will. For now, it simply parses a JSON or YAML Mufile into the core mu/pkg/api types, and prints out the result. 2016-11-15 20:30:34 +01:00
meta: Ignore IntellJ IDEA project files 2018-06-22 01:05:28 +02:00			`/.idea/`
			`*.iml`

Support TypeScript in a more first-class way This change lets us set runtime specific options in Pulumi.yaml, which will flow as arguments to the language hosts. We then teach the nodejs host that when the `typescript` is set to `true` that it should load ts-node before calling into user code. This allows using typescript natively without an explicit compile step outside of Pulumi. This works even when a tsconfig.json file is not present in the application and should provide a nicer inner loop for folks writing typescript (I'm pretty sure everyone has run into the "but I fixed that bug! Why isn't it getting picked up? Oh, I forgot to run tsc" problem. Fixes #958 2018-06-25 07:47:54 +02:00			`# VSCode creates this binary when running tests in the debugger`
			`**/debug.test`

Don't dirty work tree when running tests Because we run our golang integration tests "in tree" (due to the need to be under $GOPATH and have a vendor folder around), the "command-output" folder was getting left behind, dirtying the worktree after building. This change does two things: 1. On a succecssful run, remove the folder. 2. Ignore the folder via .gitignore (this way if a test fails and you do `git add .` you don't end up commiting this folder). 2018-06-15 00:58:37 +02:00			`# Go tests run "in tree" and this folder will linger if they fail (the integration test framework cleans`
			`# it up when they pass.)`
			`**/command-output/`
Add yarn.lock to gitignore 2018-11-13 00:34:11 +01:00
			`# By default, we don't check in yarn.lock files`
			`**/yarn.lock`