pulumi-cloud also serves as a good way to see how to build "virtual resources" out of real concrete ones

as a general pattern of componentizing things.

That’s fair. It is a killer feature for CIOs who think they’re going to do multi-cloud though 😉

@adventurous-jordan-10043 I got your example working

I've pushed my changes to make it work https://github.com/CyrusNajmabadi/pulumi-import-bug/commit/70913552c261bdc2a6beee5f58672ef19474413d

i would very much like to chat with you to help explain what i did, and to get some input from you on what you were thinking about when writing this

because this is definitely a subtle and complex area

and we want to improve it

so i'd like to figure out as best as possible how you were thinking about things and how we can help avoid problems here for all devs in the future. Thanks!

Thanks @lemon-spoon-91807 I'm looking at it right now. I've spend some time this afternoon (Paris) experimenting with different ways to structure my code and I may have more things to show you. But first I'm going to look at what you've done (thanks for your time btw)

any time!

i have an issue on my plate to write some good documentation here

your case is a good example of the types of pitfalls that one can easily hit

and we want to help people avoid that.

Yeah ok, ive just looked and this is exactly what I'm experimenting with currently. The whole wrapping the docClient resolving with a dynamic import is a common Pulumi pattern.

one min

Is it currently possible to set

cpu-options

on ec2 instances? https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.html#cpu-options-supported-instances-values

Do we continue in private or this is fine in # general ?

@adventurous-jordan-10043 i'm moving this over to the public thread

That will help keep the general thread cleaner

anyone can see it and participate

Perfect thanks

(nevermind...)

sorry, luke is educating me :)_

🎉 Hey all, we finally have some t-shirts and stickers! If you want to get your hands on them, check out this page, tell us what cool thing you're doing, and we'll send one your way. Thanks in advance for being awesome.

I’m giving a 10 minute lightning talk on getting started with Pulumi at a local meetup in a fortnight. Nervous and excited!

Is there a changelog available for packages like pulumi/aws

Blog: an intro to some essential cloud infrastructure management http://blog.pulumi.com/provisioning-and-managing-cloud-infrastructure-with-pulumi

I'm finding that when defining a nodejs lambda function via Pulumi that I must explicitly define all the required modules even though the required file already defines them... eg:

// Alexa skill - lambda function 
const alexaSkill = new cloud.Function("my-alexa-skill", (event, context, callback) => {
  // Not a big fan of redeclaring required libraries here - seems to be a limitation?
  require('ask-sdk');
  require('ask-sdk-core');
  require('ask-sdk-model');
  require('axios');
  require('moment-timezone');
  require('timezoner');
  require('node-geocoder');
  require('lodash');
  require('./alexa/my-service');
  require('./alexa/utils');

  // the alexa/index.js file has the appropriate require statements already
  const skill = require('./alexa/index');
  skill.handler(event, context, callback);
});