ha

I’m also about 4th grade with TS. 🙂 @flaky-receptionist-88878

Hi, I'm new to k8s and thought it will be a good starting point to use pulumi to learn deployments. I'm stuck on a probably trivial issue while running example from the `simple-reproducible-kubernetes-deployments`:

Previewing update of stack 'exposed-deployment'
Previewing changes:

     Type                 Name                                   Plan          Info
 +   pulumi:pulumi:Stack  exposed-deployment-exposed-deployment  create
 *   └─ global            global                                 no change     1 error

Diagnostics:
  global: global
    error: Unable to read kubectl config: invalid configuration: no configuration has been provided

error: an error occurred while advancing the preview

I'd appreciate pointing to the right path, thanks!

how do I make a stack that is owned by an organization on app.pulumi.com?

It's a bit like Git, in that you add the org name in the stack name: e.g.,

pulumi stack init myorg/mystack

Before that you'll need to add the org in the console, using the "+ Add an organization" button underneath "Select an organization"

FYI - https://pulumi.io/quickstart/install doesn't exist but is linked to by quickstarts, i.e. https://pulumi.io/quickstart/aws/tutorial-ec2-webserver.html

@big-piano-35669 got it thanks!

Is there any guide / better documentation for building a terraform bridge ?

I've just started down this journey, the AWS module has been good to look at so far

Is there a reason why I need a cloud account to be able to run a stack? We don't use GitHub for any other part of our operations.

So having to back organizations with that is really strange.

@rough-oil-1458 There is some content at https://github.com/pulumi/pulumi-terraform#adapting-a-new-terraform-provider about this - definitely happy to add more there to address any questions that come up as you work on this - feel free to drop any questions either here or in #contribute.

Also, is there documentation on exactly what data is stored on Pulumi's servers? There are cases where it's unavoidable to have sensitive, if not directly secret, data in cloud provisioning and I'd like assurances that it's not accessible.

@white-balloon-205 I just started, So im still reading how the AWS stuff works

but it might be good to have a simpler example

Im working on Trying to get VSphere plumbed

If I get to the point where I have a simple barebones build working.. with like 1 resource, ill put it up on github somewhere

@rough-oil-1458 you can look at https://github.com/jen20/pulumi-digitalocean or https://github.com/Tirke/pulumi-statuscake for simpler examples

I also made this if you need a high-level overview of how everything fits together. But it may be too high-level for you (it's skipping over tfgen and tfbridge for simplicity)

@adventurous-jordan-10043 Thank you for that!

I think status cake will help a lot

and the digital ocean one

I can now make some comparisons when i get lost

at what others did

Surprising behavior: when I return an

aws.ec2.Vpc

object as an export, it turns into its VPC ID as a string. In Terraform or CloudFormation I would expect to get the ID back, but in Pulumi these are all objects that I'm dealing with. At minimum I would have expected it to turn into, say,

{ id: "vpc-xxx" }

- stripping out fields that the exporter doesn't know what to do with.

Just to confirm my understanding, @boundless-monkey-50243, you are talking about when you export a VPC from your top level module (so it shows up as an output of your stack when you run

pulumi stack output

)?

@bitter-oil-46081 Correct. It results in an export of

{ vpc: "vpc-xxx" }

, which is inconsistent with uses of

vpc

in the code itself. (Having to remember that this

vpc

is a string is weird.)