pulumi/tests/examples/minimal/index.ts

// Copyright 2016-2018, Pulumi Corporation.  All rights reserved.

import { Config } from "@pulumi/pulumi";

let config = new Config();
console.log(`Hello, ${config.require("name")}!`);
console.log(`Psst, ${config.require("secret")}`);
Update the copyright end date to 2018. (#1068) Just what it says on the tin. 2018-03-21 20:43:21 +01:00			`// Copyright 2016-2018, Pulumi Corporation. All rights reserved.`
Add a minimal MuJS blueprint example 2017-02-09 22:36:18 +01:00
Rename pulumi package to @pulumi/pulumi (#917) In order to begin publishing our core SDK package to NPM, we will need it to be underneath the @pulumi scope so that it may remain private. Eventually, we can alias pulumi back to it. This is part of pulumi/pulumi#915. 2018-02-12 22:13:13 +01:00			`import { Config } from "@pulumi/pulumi";`
Add config to the basic/minimal test 2017-08-31 19:45:48 +02:00
Allow eliding name in pulumi.Config .ctor When this argument is not provided, we'll default to the value of pulumi.getProject(). This is what you want for application level code anyway and it matches the CLI behavior where if you don't qualify a key with a package we use the name of the current project. Fixes #1581 2018-08-03 00:27:37 +02:00			`let config = new Config();`
Add config to the basic/minimal test 2017-08-31 19:45:48 +02:00			console.log(`Hello, ${config.require("name")}!`);
Encrypt secrets in Pulumi.yaml We now encrypt secrets at rest based on a key derived from a user suplied passphrase. The system is designed in a way such that we should be able to have a different decrypter (either using a local key or some remote service in the Pulumi.com case in the future). Care is taken to ensure that we do not leak decrypted secrets into the "info" section of the checkpoint file (since we currently store the config there). In addtion, secrets are "pay for play", a passphrase is only needed when dealing with a value that's encrypted. If secure config values are not used, `pulumi` will never prompt you for a passphrase. Otherwise, we only prompt if we know we are going to need to decrypt the value. For example, `pulumi config <key>` only prompts if `<key>` is encrypted and `pulumi deploy` and friends only prompt if you are targeting a stack that has secure configuration assoicated with it. Secure values show up as unecrypted config values inside the language hosts and providers. 2017-10-19 00:37:18 +02:00			console.log(`Psst, ${config.require("secret")}`);
Add a minimal MuJS blueprint example 2017-02-09 22:36:18 +01:00