Hope someone can help me with my problem! I would like to keep the state of Pulumi in GS (

Google Storage

). What am I doing now? 1. I use the module "npm googleapis" where I log in via

OAuth2 to GCP

and get the accessToken - I have it stored under the variable. 2. I would like to use my accessToken in Pulumi to hold the state in GS. I have read about setting the

accessToken

(https://www.pulumi.com/registry/packages/gcp/installation-configuration/#configuration-reference;

pulumi config set gcp:accessToken

), but all attempts end up forcing me to log into

Pulumi Service

- and I would like to avoid that. Actually, the matter would be solved if someone would show me how to use the

pulumi login gs://

command and pass my accessToken in it. I hope there will be someone here with knowledge!

Hello! I have a question about the Pulumi Automation SDK for Python. When using an inline program running on a stack created by a

auto.LocalWorkstation

, why am I getting errors about not having set PULUMI_ACCESS_TOKEN? How should I tell the automation SDK to please use a locally managed service backend for this stack? Here’s a small snippet I think is relevant:

def get_stack(env: str, stack_name: Optional[str]) -> auto.Stack:
    if not stack_name:
        stack_name = env

    if env == "minikube":
        from .minikube import build_minikube
        program = build_minikube
    else:
        raise ValueError("Unknown environment: %s", env)

    workdir = PULUMI_WORKDIR / 'stack_name'
    if not workdir.exists():
        workdir.mkdir()

    # TODO provide secrets, etc. here
    workspace = auto.LocalWorkspace(work_dir=str(workdir), program=program)
    try:
        stack = workspace.select_stack(stack_name)
    except auto.CommandError:
        stack = workspace.create_stack(stack_name)

    assert stack is not None
    return stack

Alternately, is there a way to associate a specific PulumiFn with a specific

Pulumi.yaml

-file project definition, so that I can specify that certain target environments need to use a different PulumiFn? Then I can abandon using the automation API entirely and just use the

pulumi

CLI.

Whats the difference between the azure-native provider and azure classic? I've been using azure-native.authorization.PolicyDefinition but have hit a resource where it doesn't look like it supports specifying a management group, where as with Azure classic it does. So I'm not sure which provider I should be targeting to use(and why azure-native would be missing this)? edit. Oh damn I just realized there is a azure-native.authorization.PolicyDefinitionAtManagementGroup which I didn't notice. This looks like it will do what I'm after though I'm not sure why they are separate.

The official docs didn’t give me a fast answer to this elementary question. Do stack references of Pulumi work for resource objects, or are they only for transferring string IDs? Can we create an AWS security group in an "infra" stack and refer to it within a "service" stack directly as a resource object, or do I have to run a lookup query in the latter?

Is there a way to mark variable as not a secret?

kubeconfig_path = pulumi.Output.all(cluster_kubeconfig, cluster.name).apply(lambda args: update_kubeconfig(*args))
pulumi.export("kubeconfigPath", kubeconfig_path)

kubeconfig_path shows as [secret] while it's clearly not.

Hi!! I am trying to use pulumi from my local computer. I am trying to install

pulumi-azure-native

for python3.7 and it get stuck for a long time. how can I install it anyway?

In GKE can't turn on default-pool autoscaling (issue) I wonder if someone has a workaround? Something like below that actually works?

defaul_pool =  container.NodePool(
        "default-pool",
        # REQUIRES CLUSTER NAME
        location="europe-central2-a",
        autoscaling={..}
        ..
)

cluster = container.Cluster(
        "mycluster",
        location="europe-central2-a",
        node_pools=[default_pool],
        ..
)

Hi there! Is there anyone else having the same problem as me?I’m using Golang, When exactly followed, EKS has no node groups. Using AWS Elastic Kubernetes Service (EKS) | Crosswalk | Pulumi Docs

Howdy ya’ll, Question about doing things the proper pulumi way - What is the proper way to write a deployment library that can be used across the pulumi supported languages? (specifically want to write once if possible, and use in both C# and Typescript, preferably writing only in typescript) or do I need to write and maintain two deployment libraries?

Hi all, I'm trying to understand the best practices around managing a lot of different k8s clusters with one pulumi codebase. We're going to start with something like a dozen clusters or so, but plan to scale that up to the hundreds within a year or so, across several different cloud providers. Would it be best to think about making one project for each cluster? Or just one project for each cloud provider, with a stack for each k8s cluster? Assuming the latter, the only difference in each stack should be what's in the yaml, right? But should each of those yamls be in separate directories? Any guidance or examples would be greatly appreciated, thank you!

Hey 🙂 We're currently using Pulumi cloud, and thinking about moving to a self-hosted s3 backend. Can someone explain to me exactly what synchronization features will I lose?

Hi, I'm setting up pulumi in github actions workflow deploying into gcp and I'm getting: error: failed to load application credentials. pulumi up works fine locally using a gcp credential.json file. i.e. pulumi config set gcp:credentials "~/poc-88ee30ae551c.json" However, this stores the local path which obviously won't work in the action. What I'd like to do is store the contents of the credentials.json file in the pulumi config. But I can't get this to work with a command like this: pulumi config set gcp:credentials '{ "type": "service_account", "project_id": "poc", "private_key_id": "88ee30ae5...ccaa0c565", "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEvgIB...KHsvMXd\n-----END PRIVATE KEY-----\n", "client_email": "pulumi@poc.iam.gserviceaccount.com", "client_id": "116580898...632877949", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://oauth2.googleapis.com/token", "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs", "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/pulumi%40poc.iam.gserviceaccount.com"}' --secret I get: error: accepts between 1 and 2 arg(s), received 6 Am I headed in the right direction? Any help is appreciated.

Hello everybody, I'm trying to apply some changes in my stack, however, any command I run end with the response: "Unable to describe task definition." Anyone know how I release the Fargate state?

Hello, I’m looking for documentation on how to approach setting up Service Connect within an ECS cluster for two fargate services. The codebase I’m working on leverages AWS Crosswalk’s FargateService implementation instead of the AWS Classic Service implementation, but unlike classic does not have any obvious configuration for Service Connect (maybe SC is too new). Does anyone have any examples or recipes? Would I be better off just setting up Service Discovery? Thanks!

Hi folks - just started trying to use Pulumi and the first thing I run into is trying to get MFA and Assume Role working. Is there a suggested approach or solution? I found the existing ticket in #1366, but there’s no workaround that seems to be “accepted”.

Hi all, bit of a beginner question here. I am using the databricks provider with nodejs SDK, and after I’ve put my credentials into the YAML, I’m wondering how I can access information about the user & workspace being worked on from within my js code?

Due to Pulumi not playing well with GKE in Python I'm trying to do some workaround by directly calling

gcloud

but I'm lost and can't find much examples. With the code below I get

error: unrecognized resource type (Check): gcp:myaccount:Cluster

class MyCluster(pulumi.CustomResource):
    def __init__(self, name, opts=None):
        super().__init__("gcp:myaccount:Cluster", name, {}, opts)

    def create(self):
        # TODO: Call gcloud directly to create cluster
        super().create()

    def delete(self):
        # TODO: Call gcloud directly to kill cluster
        super().delete()


cluster = MyCluster("mycluster")

What is

*:**:**

supposed to be?

Hi Guys, I'm having problems with a second machine. I used pulumi on one and life was good. But my other machine doesn't seem to want to work. I upgraded python to 3.7.5 as it was < 3.6. After installing pulumi and trying to up the stack I get the following. `error: failed to discover plugin requirements: calling `python -m pip list -v --format json`: exit status 1` I tried running it against the virtual environment that gets created and indeed there was no pip. But this venv is created by pulumi. e.g

/home/user1/code/user1-pulumi-testing/venv/bin/python -m pip list -v --format json

/home/user1/code/user1-pulumi-testing/venv/bin/python: No module named pip

I'm not sure how to try and get this sorted.

I'm building an ecs cluster and attempting to declare subnets I have 3 public and 3 private subnets under 2 different variables is there a way to include both under subnets = or does leaving that key out automatically select all

Hi team, was wondering what program do I use to view the

*.cpu

and

*.mem

files when running

pulumi up --profiling ..

?

I see in the documentation for component resources that it's recommended to register outputs. What can I do with them once they are registered? Is there a way to access them for other resources that depend on them?

I have confirmed my order of swags . But I didn't get any mail. So how to track my order?

Hey all, I have been exploring a way to tag a docker image when pushing it with AWS Crosswalk. Crosswalk implementation. Currently, this implementation does not tag the images it pushes to ECR.

repository = awsx.ecr.Respository(...)

image = awsx.ecr.Image(
    "scheduler",
    path="../",
    dockerfile="scheduler/Dockerfile",
    extra_options={
        "-t",
        "1.0.0"
    },
    args={
       ...
    },
)

This implementation does, but is inconsistent and uses Pulumi-docker. I’m currently getting bugs fairly frequently trying to build and push this way, so Crosswalk would be preferable as it was very consistent (just didn’t tag).

repository = awsx.ecr.Respository(...)

image = docker.Image(
    name="scheduler",
    image_name=repository.url.apply(lambda url: f"{url}:{scheduler_version}"),
    build=docker.DockerBuild(
        context="../",  # type: ignore
        dockerfile="scheduler/Dockerfile",  # type: ignore
        args={
            ...
        }
    ),
    registry=None,
)

Is there a way I’m not seeing to tag using AWSx?

Hi all, Bit of a long post, but I am trying to figure out the best way to organize a dynamic set of Pulumi projects and stacks. I am planning to use Pulumi to deploy resources to Kubernetes and cloud providers on behalf of our customers. Some of our customers pay us to manage their infrastructure, and some of them prefer to manage it themselves. The first group deploy workloads to infrastructure that we manage, while the second group will need to execute pulumi projects using their own cloud credentials. There are serveral apps and microservices that customers will want to deploy, and a few of these will be deployed multiple times per customer. A dashboard app is first deployed for a customer. The dashboard will make use of the pulumi automation API to deploy additional apps and microservices at the customers request. I am not sure how best to organize the projects and stacks in Pulumi. Option 1: One project per customer workload, with one stack per environment. /my-organization/infra/qa (for our infrastructure) /my-organization/infra/prod (for our infrastructure) /my-organization/customer-a-dashboard/qa /my-organization/customer-a-dashboard/prod /my-organization/customer-a-app1/qa /my-organization/customer-a-app1/prod /my-organization/customer-a-app2/qa /my-organization/customer-a-app2/prod /my-organization/customer-b-app1/qa /my-organization/customer-b-app1/prod /my-organization/customer-b-app2/qa /my-organization/customer-b-app2/prod Each time a customer deploys a new app, a new project would be created. When a customer removes an app, the project would be destroyed. Option 2: One project per customer, with one stack per environment. /my-organization/infra/qa (for our infrastructure) /my-organization/infra/prod (for our infrastructure) /my-organization/customer-a/qa /my-organization/customer-a/prod /my-organization/customer-b/qa /my-organization/customer-b/prod

Hi folks ... I don't see how to represent Container Ports in Python ... anybody have a simple example to share? Thanks much!

Hi, all, when I run below gitlab CI I get this error. Any tips where the problem might be ?

Previewing update (dev):
error: could not load plugin for gcp provider 'urn:pulumi:dev::xxxx::pulumi:providers:gcp::default': Could not automatically download and install resource plugin 'pulumi-resource-gcp', install the plugin using `pulumi plugin install resource gcp`.
Underlying error: 401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-gcp/releases/latest>

If I add

pulumi plugin install resource gcp

I get:

error: 401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-gcp/releases/latest>

default:
    image: pulumi/pulumi:latest
  
  stages:
    - deploy-preview
    - deploy-update
  
  deploy-preview:
    stage: deploy-preview
    rules:
      - if: $CI_COMMIT_BANCH == "dev"
      - if: $CI_PIPELINE_SOURCE == "push"
        when: always
    script:
      - export PULUMI_CONFIG_PASSPHRASE=""
      - pulumi login <gs://xxxxxxxxxx>
      - pulumi stack select ${CI_COMMIT_BRANCH}
      - pulumi config set gcp:project xxxxxxxxxx
      - pulumi config set gcp:region xxxxxxxxxx
      - pulumi preview
  
  deploy-update:
    stage: deploy-update
    rules:
      - if: $CI_COMMIT_BANCH == "dev"
      - if: $CI_PIPELINE_SOURCE == "push"
        when: manual
    script:
      - export PULUMI_CONFIG_PASSPHRASE=""
      - pulumi login <gs://xxxxxxxxxx>
      - pulumi stack select ${CI_COMMIT_BRANCH}
      - pulumi config set gcp:project xxxxxxxxxx
      - pulumi config set gcp:region xxxxxxxxxx
      - pulumi update --yes

ha, just saw on General channel there are some issues, so it's not me I think

Hi , I am new to Pulumi and exploring Azure. I am trying to get private ip address of nic that I created.

p_vm_nic[vnet][subnet] = azure_native.network.NetworkInterface(p_nic_name,
                                                                                   enable_accelerated_networking=True,
                                                                                   network_security_group = azure_native.network.NetworkSecurityGroupArgs(id=nsg_out[vnet].id),
                                                                                   location=location,
                                                                                   network_interface_name=p_nic_name,
                                                                                   resource_group_name=rg_out.name,
                                                                                   ip_configurations = [azure_native.network.NetworkInterfaceIPConfigurationArgs(name=p_nic_name, public_ip_address=azure_native.network.PublicIPAddressArgs(id=p_public_ip[vnet][subnet].id), subnet=azure_native.network.SubnetArgs(id=subnet_out[vnet][subnet].id), private_ip_allocation_method="Dynamic")]
                                                                                   )

I tried several things along this line, no luck. Any help is appreciated. Thanks in advance.

private_ip = p_vm_nic[vnet][subnet].ip_configurations.apply(lambda ip_configurations: ip_configurations[0]['private_ip_address'])

Hello, I am having some issues regarding python's`pulumi.automation` in reference to getting gitlab.com to show the pending changes after a

preview

in a merge request pipeline.I have followed the docs and have a sucessful 200 response when running gitlab's test here: I also created a very small sucessful test case where I use pulumi's cli rather than the automation tools: I believe I am missing something with respect to setting up a preview through

pulumi.automation

. The preview itself is sucessful, but the webhook does not fire to produce the preview on gitlab ui. Can someone point me in the right direction?