https://pulumi.com logo
Docs
Join the conversationJoin Slack
Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-cdk
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumi-service
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by Linen
general
  • h

    happy-parrot-60128

    05/24/2019, 9:59 AM
    I tried using io-ts but have run into the issues around how modules get packaged (https://github.com/pulumi/pulumi-aws/issues/249). Unfortunately, using an
    await import
    doesn’t work well as you typically declare your io-ts types globally. Also the
    cloud-aws:functionIncludePackages: io-ts
    doesn’t seem to change anything. Should I look at using custom packaging and import the assets or is there any other approaches I could try?
  • c

    creamy-jelly-91590

    05/24/2019, 12:22 PM
    Is it at all (going to be) possible to go from TF to Pulumi without recreating all resources?
    t
    • 2
    • 2
  • b

    billions-mechanic-26704

    05/24/2019, 12:52 PM
    Hi people,. I am new on pulumi world. I have started to use terraform from a couple of months, and I would like to understand a little bit more the benefits, pros and cons with relation to pulumi and other things ... Currently I am working in a CI/CD pipeline on Azure DevOps, and I am going to certifying me in Azure DevOps, My daily work in with Kubernetes and some specific DevOps workflow, all using AZure Cloud platform and some other tools like terraform, helm, kong as a mesh service ... I would like to try pulumi, because python is a very powerful language, and I would like to use it, instead of YAML files, of course I want to continue using the other tools
  • b

    billions-mechanic-26704

    05/24/2019, 12:59 PM
    What about infrastructure state in pulumi, Can I store it and manage it ?
    g
    c
    s
    • 4
    • 21
  • g

    gentle-diamond-70147

    05/24/2019, 1:06 PM
    We have a Pulumi Azure Pipelines Task in the Azure marketplace, FYI - https://marketplace.visualstudio.com/items?itemName=pulumi.build-and-release-task.
    ❤️ 1
    c
    • 2
    • 1
  • b

    bitter-island-28909

    05/24/2019, 1:59 PM
    Recently started experiencing some unexpected behavior where, after running
    pulumi refresh
    , Pulumi now wants to spuriously update or replace a bunch of resources that I can assert haven’t actually changed. Some examples of diffs that look wrong to me (on various resources):
    ~ records: [
        ~ [0]: "10.3.0.222" => output<string>
    ]
    
    ~ memory                 : "512" => 512
    
    - volumes                : []
    
     ~ applications               : [
        ~ [0]: "Spark" => "Hadoop"
        ~ [2]: "Hadoop" => "Presto"
        ~ [3]: "Presto" => "Spark"
    ]
    This occurs immediately after a sequence of
    pulumi up
    ,
    pulumi refresh
    ,
    pulumi up
    , without any alteration of my scripts or deliberate modification of deployed resources.
    w
    • 2
    • 7
  • o

    orange-policeman-59119

    05/24/2019, 5:41 PM
    I'm having an issue where a K8s deployment that is spun up via Helm chart consistently behaves in two ways: 1. A second replicaset is created when a deployment is updated (makes sense), that spins up a new replicaset, that starts up, and the first doesn't go away (???) 2. On refresh it then thinks the deployment is in an unhealthy state and subsequent deployments fail with:
    Diagnostics:
      kubernetes:extensions:Deployment ([redacted]):
        warning: Refreshed resource is in an unhealthy state:
        * Resource '[redacted]' was created but failed to initialize
        * Minimum number of Pods to consider the application live was not attained
    Here's what the resources look like:
    $ kubectl -n ... get deployment
    NAME         READY     UP-TO-DATE   AVAILABLE   AGE
    [deployment] 3/3       3            3           11h
    $ kubectl -n ... get rs
    NAME    DESIRED   CURRENT   READY     AGE
    [old]   0         0         0         11h
    [new]   3         3         3         6m4s
    c
    • 2
    • 32
  • b

    busy-umbrella-36067

    05/24/2019, 5:42 PM
    Is there a known bug with
    values
    using
    kubernetes.helm.v2.Chart
    ?
    I’m having issues with values not being applied to the templates, specifically the
    targetPorts
    on an Ingress Chart
    Chart had the wrong values documented, my bad.
    // create ingress controller
        const ingressController = new k8s.helm.v2.Chart(
          name,
          {
            fetchOpts: {
              repo: "<https://helm.nginx.com/stable>"
            },
            chart: "nginx-ingress",
            version: "0.3.0",
            values: {
              controller: {
                service: {
                  targetPorts: {
                    https: "http",
                    http: "http"
                  },
                  annotations: {
                    "<http://service.beta.kubernetes.io/aws-load-balancer-ssl-cert|service.beta.kubernetes.io/aws-load-balancer-ssl-cert>": certificate.arn,
                    "<http://service.beta.kubernetes.io/aws-load-balancer-backend-protocol|service.beta.kubernetes.io/aws-load-balancer-backend-protocol>": "http",
                    "<http://service.beta.kubernetes.io/aws-load-balancer-ssl-ports|service.beta.kubernetes.io/aws-load-balancer-ssl-ports>": "https",
                    "<http://service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout|service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout>": "3600"
                  }
                }
              }
            }
          }, {});
      }
    c
    • 2
    • 7
  • o

    orange-policeman-59119

    05/24/2019, 6:34 PM
    @creamy-potato-29402 was there a regression in the Kubernetes Helm provider not rendering
    Input<>
    values? I'm seeing this since updating
    @pulumi/kubernetes
    to 0.23:
    Error: render error in "[redacted]/secret.yaml": template: [redacted]/secret.yaml:15:49: executing "[redacted]/secret.yaml" at <b64enc>: wrong type for value; expected string; got map[string]interface {}
    Only change was updating the Pulumi kubernetes provider.
    c
    • 2
    • 10
  • o

    orange-policeman-59119

    05/24/2019, 6:35 PM
    Previously I was passing in
    values: { foo: { bar: { secretValue: $someInput<string> }}}
  • a

    average-dream-51210

    05/25/2019, 11:50 PM
    Is there an example anywhere of aws VPC with public/private subnets spanning multiple AZs in Pulumi?
    w
    • 2
    • 9
  • l

    little-dinner-9110

    05/26/2019, 2:18 AM
    Hello. am wondering what "individual use" means in "Pulumi Community Edition is free forever for unlimited individual use."
    w
    • 2
    • 2
  • l

    little-dinner-9110

    05/26/2019, 2:20 AM
    I guess it means not in the context of a business or company, even if not-for-profit institution? are there details somewhere I refer to?
  • p

    proud-artist-4864

    05/27/2019, 7:35 AM
    The software source contains licensing information showing that it is licensed under the Apache License Version 2.0.
  • s

    square-plumber-80712

    05/27/2019, 8:41 AM
    Hello! Quick question, is there any GCP-equivalent of this tutorial (using @pulumi/cloud) https://pulumi.io/quickstart/cloudfx/tutorial-service.html? All the best & thank you for your great work!
  • j

    jolly-egg-4894

    05/27/2019, 9:58 AM
    Well that example uses either AWS Fargate or what I’m guessing is Azure Container Service For GCP are you using GKE? You’d probably want to read here: https://pulumi.io/reference/pkg/nodejs/@pulumi/gcp/container/
    👍 1
    s
    • 2
    • 5
  • c

    colossal-room-15708

    05/27/2019, 11:20 AM
    Just bumping this one up: https://pulumi-community.slack.com/archives/C84L4E3N1/p1558037668491900
  • f

    faint-motherboard-95438

    05/28/2019, 11:12 AM
    what did you guys change about providers ? I can’t update my platform anymore and I have no idea what I have to do to fix it. I tried to downgrade packages but I’m unable to get back to a working state…
    index.ts(109,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
        index.ts(134,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
        index.ts(170,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
        index.ts(188,5): error TS2322: Type '{ gcp: Provider; kubernetes: Provider; }' is not assignable to type 'Record<string, ProviderResource>'.
    I’m creating providers for gcp and kubernetes with
    new gcp.Provider()
    and
    new k8s.Provider()
    from
    @pulumi/gcp
    and
    @pulumi/kubernetes
    respectively and I’m passing them down in all my components
    opts
    argument. Everything was perfectly working before…
    b
    s
    b
    • 4
    • 21
  • g

    gray-hair-49169

    05/28/2019, 12:13 PM
    I would like to deploy a simply postgreSQL in Azure, but the login failed. Anybody got an idea?
    const testPostgresServer = new azure.postgresql.Server("testserver", {
        administratorLogin: "USER",
        administratorLoginPassword: "PASS",
        location: config.location,
        name: `${config.prefix}-postgresql-01`,
        resourceGroupName: config.resourceGroup.name,
        sku: {
            capacity: 1,
            family: "Gen5",
            name: "B_Gen5_1",
            tier: "Basic",
        },
        sslEnforcement: "Enabled",
        storageProfile: {
            backupRetentionDays: 7,
            geoRedundantBackup: "Disabled",
            storageMb: 5120,
        },
        version: "9.5",
    });
    
    const testConfiguration = new azure.postgresql.Configuration("testconf", {
        name: "backslash_quote",
        resourceGroupName: config.resourceGroup.name,
        serverName: testPostgresServer.name,
        value: "on",
    });
    
    const testDatabase = new azure.postgresql.Database("testdb", {
        charset: "UTF8",
        collation: "English_United States.1252",
        name: "exampledb",
        resourceGroupName: config.resourceGroup.name,
        serverName: testPostgresServer.name,
    });
    Thanks 🙂
  • s

    stocky-spoon-28903

    05/28/2019, 12:18 PM
    HBA is host based authentication iirc
  • s

    stocky-spoon-28903

    05/28/2019, 12:21 PM
    IIRC (it’s been a while since I looked at Postgres on azure!) you need a security group to allow your client access via the firewall
    ✔️ 1
    g
    • 2
    • 2
  • b

    better-rainbow-14549

    05/28/2019, 5:21 PM
    how do we migrate AKS from 0.18.4 to 0.18.5 please, the API has changed quite a lot
  • b

    better-rainbow-14549

    05/28/2019, 5:21 PM
    will agentPoolProfile: {...} --> agentPoolProfiles: [{...}] work
  • s

    stocky-spoon-28903

    05/28/2019, 5:23 PM
    I believe that is the case, yes @sparse-insurance-40223
  • b

    better-rainbow-14549

    05/28/2019, 5:23 PM
    cheers - just wanted to check cos this is 2 layers deep in an NPM and it will be a pain if it doesnt work 😄
  • b

    better-rainbow-14549

    05/28/2019, 5:23 PM
    can't even get a preview without publishing it twice :s
  • s

    stocky-spoon-28903

    05/28/2019, 5:24 PM
    Try it by editing in
    node_modules
    directly to get a preview?
  • s

    stocky-spoon-28903

    05/28/2019, 5:24 PM
    Or
    yarn link
    ?
  • s

    stocky-spoon-28903

    05/28/2019, 5:24 PM
    (or
    npm link
    etc)
  • b

    better-rainbow-14549

    05/28/2019, 5:24 PM
    i've never got npm link to work with pulumi
Powered by Linen
Title
b

better-rainbow-14549

05/28/2019, 5:24 PM
i've never got npm link to work with pulumi
View count: 1