Hi I'm working with pulumi python, after using

k8s.yaml.ConfigFile

and

k8s.yaml.ConfigGroup

for a few months with no issues, I'm currently seeing an issue when previewing a new stack with these elements. this is a stuck trace.

error: Traceback (most recent call last):
      File "/nix/store/4a6xm29r8fpn80ipkqyqhn31mhh7pai6-pulumi-3.32.1/bin/pulumi-language-python-exec", line 107, in <module>
        loop.run_until_complete(coro)
      File "/nix/store/328bxidfhv01x138sjynkzswiskrk1yd-python3-3.9.12/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
        return future.result()
      File "/nix/store/s6zf9dbdk4b9cajc6plcw72gg8mgvybq-python3-3.9.12-env/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 126, in run_in_stack
        await run_pulumi_func(lambda: Stack(func))
      File "/nix/store/s6zf9dbdk4b9cajc6plcw72gg8mgvybq-python3-3.9.12-env/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 49, in run_pulumi_func
        func()
      File "/nix/store/s6zf9dbdk4b9cajc6plcw72gg8mgvybq-python3-3.9.12-env/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 126, in <lambda>
        await run_pulumi_func(lambda: Stack(func))
      File "/nix/store/s6zf9dbdk4b9cajc6plcw72gg8mgvybq-python3-3.9.12-env/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 149, in __init__
        func()
      File "/nix/store/4a6xm29r8fpn80ipkqyqhn31mhh7pai6-pulumi-3.32.1/bin/pulumi-language-python-exec", line 106, in <lambda>
        coro = pulumi.runtime.run_in_stack(lambda: runpy.run_path(args.PROGRAM, run_name='__main__'))
      File "/nix/store/328bxidfhv01x138sjynkzswiskrk1yd-python3-3.9.12/lib/python3.9/runpy.py", line 285, in run_path
        return _run_code(code, mod_globals, init_globals,
      File "/nix/store/328bxidfhv01x138sjynkzswiskrk1yd-python3-3.9.12/lib/python3.9/runpy.py", line 87, in _run_code
        exec(code, run_globals)
      File "/Users/uritwig/workspace/arnac/infra/pulumi/./__main__.py", line 19, in <module>
        managed_infra.deploy()
      File "/Users/uritwig/workspace/arnac/infra/pulumi/stacks/managed_infra.py", line 224, in deploy
        create_cluster(network)
      File "/Users/uritwig/workspace/arnac/infra/pulumi/stacks/managed_infra.py", line 195, in create_cluster
        cluster = Cluster(cluster_args)
      File "/Users/uritwig/workspace/arnac/infra/pulumi/components/cluster/cluster.py", line 112, in __init__
        self._create_enclave_smarter_device()
      File "/Users/uritwig/workspace/arnac/infra/pulumi/components/cluster/cluster.py", line 208, in _create_enclave_smarter_device
        self.smarter_device = k8s.yaml.ConfigFile(
      File "/nix/store/s6zf9dbdk4b9cajc6plcw72gg8mgvybq-python3-3.9.12-env/lib/python3.9/site-packages/pulumi_kubernetes/yaml/yaml.py", line 348, in __init__
        __ret__ = pulumi.runtime.invoke('kubernetes:yaml:decode', {'text': text}, invoke_opts).value['result']
    TypeError: 'NoneType' object is not subscriptable
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

removing these elements removes the issue.I'm using pulumi 3.32.1 with this is the k8s pluging when running

pulumi plugin ls

kubernetes                resource  3.20.3   78 MB   2 hours ago  2 hours ago
kubernetes                resource  3.20.2   78 MB   2 hours ago  2 hours ago
kubernetes                resource  3.19.0   79 MB   2 hours ago  2 hours ago

What can I do to fix this?

is this a dead project? https://github.com/pulumi/eks-blueprint

Hello. Is there a way to mark a component as protected without making every child protected too? Use case: a "Service" component is marked as protected so that we don't accidentally remove a whole service definition but i dont want the children to be irreplaceable unless explicitly marked as such. One workaround would be to make a no-op child resource of the component and protect that.. but now i'd get charged for that by pulumi cloud. 😕

How do you run pulumi from public repositories? I want to build IaC in the open, but if I have my secret keys as env variables in the github repository, then anyone who can fork and open a PR will be able to also destroy all of my infra. Is there a way to protect from this?

Hi, How do I refer one pulumi stack in another pulumi stack? I am using Python inline method to write my stack. My both stack is in same project. I am doing something like below, any suggestions?

# stack1
def program1():
    pulumi.export("ec2_role_arn", ec2_role.arn)

# stack2
def program2():
    ref = pulumi.StackReference("stack1")
    ec2_role = ref.require_output("ec2_role_arn")
    # do something with ec2 role arn

Hi, I need to enable Document AI in GCP, is there any way to do this through pulumi ?

👋 Hi everyone! I'm rather new to Pulumi and am hoping for an assist here. When attempting to deploy multiple instances of the same Pulumi program via a Next.JS API (in Typescript) with the Automation API, I run into this error for every concurrent cloud component in my stack:

'failed to register new resource <INSERT_CLOUD_RESOURCE_NAME_HERE>: Resource monitor is terminating'

Additionally, I was able to see this error once, implying that there's only one instance of the engine running in my API:

Error: Program run without the Pulumi engine available; re-run using the `pulumi` CLI

To be sure, my deployment works just fine when the function is called once, further hinting at the notion that I'm referencing an already busy process. I'd love to know if there's a way to force Pulumi to spin up another process or instance whenever a new deployment is requested, but I could not find any documentation around it, so I'd love some pointers!

Hey, everyone! Scratching my head on a weird issue and was wondering if maybe someone else had seen this before. I’m using pulumi to bootstrap a cluster on eks in order to test our agents during CI/CD. The eks cluster is successfully , created but for some reason the nodes get stuck in a not ready state. Trying to get the logs from any pod returns “Error from server (InternalError): Internal error occurred: Authorization error (user=kube-apiserver-kubelet-client, verb=get, resource=nodes, subresource=proxy)” … so its hard to debug what exactly is going on. I also can’t connect to underlying instance itself (ssh times out) so Im sort of flying blind. Nothing can get scheduled, because of the node issue. Seems to be related to kubelet, because all of the nodes have the following for all of their conditions

NodeStatusUnknown  Kubelet stopped posting node status.

Im also just following the standard tutorial from pulumi docs.

Hello, how do you set

pulumi config

inside the CI pipeline? This seems to be a problem that config has to be present before CI runs but this presents another problem that the config value is already exposed to the code which has not been merged yet. Is there any recommendation to avoid this problem?

The Pulumi GitHub SDK doesn’t seem to ignore the

etag

reference on objects. I wrote up a quick issue in regards to this. Is there any workaround or fix for this? This is causing our stack to take a long time to refresh and update resources as this etag is referenced on every repo, branch, team, and member… https://github.com/pulumi/pulumi-github/issues/230

How do I pulumify this import of a function app as an API in Azure API Management.? https://docs.microsoft.com/en-us/azure/api-management/import-function-app-as-api

I want to encrypt the binary file using pulumi secret which can be used inside be pod. Can someone pl suggest a way to do it

is this a bug?

Hi, i want to know if tf2pulumi can convert hcl to go language, i just see https://www.pulumi.com/docs/guides/adopting/from_terraform/ that tf2pulumi generate a Pulumi TypeScript program, it doesn't matter what language your project created

Do people keep their infrastructure as code with their application or in a separate infrastructure repo?

Cross-posting here to hopefully get some help - https://pulumi-community.slack.com/archives/CRVK66N5U/p1660560451624099

Is it possible to use pulumi Service with self managed backend ?

What does error mean? its not helpful at all

Diagnostics:
  pulumi:pulumi:Stack (allrites-infrastructure-dev):
    error: Running program '/home/k1ng/projects/allrites-infra' failed with an unhandled exception:
    TypeError: Cannot read properties of null (reading 'data')
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/nodegroup.ts:501:95
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/output.ts:383:31
        at Generator.next (<anonymous>)
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:21:71
        at new Promise (<anonymous>)
        at __awaiter (/home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:17:12)
        at applyHelperAsync (/home/k1ng/projects/allrites-infra/node_modules/@pulumi/pulumi/output.js:229:12)
        at /home/k1ng/projects/allrites-infra/node_modules/@pulumi/output.ts:302:65
        at processTicksAndRejections (node:internal/process/task_queues:95:5)

https://www.pulumi.com/registry/packages/docker/installation-configuration/ does not show the java way, how good currently state of pulumi for docker with java..

Hello folks, I’m struggling with the confluent cloud API, that we’re using to create a Kafka related resources (topics, SA, api keys, and what not). We have properly configured the GCP Marketplace integration, and I’m acting on the confluent platform as a member of my organization, but can’t manage to create a kafka topic. Any ideas what’s failing?

const topic = new KafkaTopic(
  args.name,
  {
    topicName: args.name,
    kafkaCluster: { id: cluster.id },
    restEndpoint: cluster.restEndpoint,
    credentials: {
      key: clusterSA.apiKey.name,
      secret: clusterSA.apiKey.secret,
     },
   },
 { parent: this }
);

   Type                                    Name                    Status                  Info
     pulumi:pulumi:Stack                     confluent-test          **failed**              1 error; 2 messages
     └─ nesto:kafka                          test                                            
 +      ├─ confluentcloud:index:KafkaTopic   test                    **creating failed**     1 error
 +      └─ confluentcloud:index:RoleBinding  test-environment-admin  **creating failed**     1 error
 
Diagnostics:
  pulumi:pulumi:Stack (confluent-test):
    2022/08/17 08:19:24 [DEBUG] POST <https://pkc-41voz>.<region>.gcp.confluent.cloud:443/kafka/v3/clusters/<cluster-id>/topics
 
    error: update failed
 
  confluentcloud:index:KafkaTopic (test):
    error: 1 error occurred:
        * error creating Kafka Topic: 401 Unauthorized: Unauthorized

I also tried it creating a Provider resource, then passing the latter as

opts

. Didn’t work either. Any insights will be greatly appreciated. Have a nice day,

Hey folks! I was wondering if the

Pulumi Service REST API

has a way of exporting project level configurations.

Just a heads up - there’s a syntax error in this blog post https://www.pulumi.com/blog/scheduling-serverless/

const emptyTrashSchedule: aws.cloudwatch.EventRuleEventSubscription = aws.cloudwatch.onSchedule(
  "emptyTrash",
  "cron(0 23 ? * FRI *)",
  emptyTrash

// Export the name of the bucket
export const bucketName = trashBucket.id;
);

The parens are in the wrong place

Does Pulumi has any option to generate yaml file that code is actually is..

Hello, according to the ec2.RouteTable documentation:

NOTE on Route Tables and Routes: This provider currently provides both a standalone Route resource and a Route Table resource with routes defined in-line. At this time you cannot use a Route Table with in-line routes in conjunction with any Route resources. Doing so will cause a conflict of rule settings and will overwrite rules.

But importing ec2.RouteTable resources automatically attach the Routes as inline. Does it mean that I can not create more individual routes using ec2.Route because then it will override the ones already imported on the ec2.RouteTable (because those are inline)?.

Hey all; I'm wondering if anyone has any patterns/tips when it comes to sharing and hydrating resources across stack boundaries/using stack references. Currently, I'm thinking that a good idea might be to adopt a pattern where my `ComponentResource`s look something like this:

class MyResource extends pulumi.ComponentResource {
  static create(name, args, opts): MyResource {
    const foo = new aws.Foo(...)
    const bar = new aws.Bar(...)

    return new this(foo, bar)
  }

  static fromExisting(fooId, barId) {
    const foo = aws.Foo.getFoo(fooId)
    const bar = aws.Bar.getBar(barId)

    return new this(foo, bar)
  }

  private constructor(foo, bar) {
    this.foo = foo
    this.bar = bar
  }

  toOutputs() {
    return {
      fooId: this.foo.id,
      barId: this.bar.id,
    }
  }
}

Or something like that -- basically a pattern in which custom components can be serialised to something a stack can return as outputs (

toOutputs

), a static function for hydrating from those outputs (

fromExisting

) and a

create

static method that creates a new resource (thus making the constructor private and dumb). Has anyone tried this/any thoughts on this?

I also wonder if this the purpose of `initialize`/`getData` in

ComponentResource

? So that it's easier to make construction pick between "create something new" and "reference something existing"?

awsx.ec2.Vpc

seems to have this sort of pattern but again open to any feedback/suggestions. There is https://github.com/pulumi/pulumi/issues/4133 on GitHub but it's not really gone anywhere yet. Thanks!

package com.tejasoft.devops.iac.pulumi.aws;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.eks.Cluster;

public final class AWSEKSPulumiApp
{
    public static void main(final String[] aArgs) {
       Pulumi.run(AWSEKSPulumiApp::stack);
    }

    private static void stack(final Context aContext) {
       final var cluster = new Cluster("eks-cluster");
       aContext.export("kubeconfig", cluster.kubeconfig());
    }
}

when this is executed the command

pulumi stack output

gives out put as

Current stack outputs (0):

No output values currently in this stack

any reason, I expect it to show kubeconfig