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
  • f

    faint-motherboard-95438

    01/02/2019, 6:28 PM
    I have a class extending
    pulumi.ComponentResource
    , let’s call it
    MyComponent
    , creating in its
    constructor
    a
    k8s.core.v1.ConfigMap
    and a
    k8s.helm.v2.Chart
    the former getting a direct reference to it in the later
    values
    args. Both have their
    opts
    like
    { parent: this }
    ,
    this
    obviously referencing
    MyComponent
    .
    MyComponent
    is called with
    opts
    like
    { providers: { kubernetes: k8sProvider /* a working k8s.Provider instance */ } }
    In this situation I get this error :
    error: Error: Explicit providers may not be used with component resources
    Where things get weirder is that if I remove
    opts
    along with the parent reference from the
    ConfigMap
    (and only from this one), the error disappear. I tracked down the error in
    pulumi.ComponentResource
    :
    if (opts.provider !== undefined) {
                throw new errors_1.ResourceError("Explicit providers may not be used with component resources", opts.parent);
            }
    That does not make any sense for me in this situation, I don’t even set an
    opts.provider
    anywhere. Is this intended (and if so I could use some help to understand it) or should I open an issue ?
    w
    • 2
    • 4
  • w

    white-balloon-205

    01/02/2019, 7:59 PM
    Hello everyone ! First a happy new year to all of you. And wishing to accomplish great things with pulumi to @echoing-match-29901 for this new year to come.
    Thanks @faint-motherboard-95438! Happy new years to you and everyone else here in the Pulumi community. We're looking forward to an exciting 2019 for Pulumi!
    👏 1
  • c

    cuddly-eye-68174

    01/03/2019, 10:24 AM
    Hi Guys, just a quick feedback. Pulumi 0.16.9 is working as fast as 0.16.6 under Python 🙂 so thanks i was able to upgrade. 😉 - Happy New Year and keep going! 💪 Thanks so much!!!
    🎉 3
  • r

    rough-oil-1458

    01/03/2019, 10:20 PM
    Has anyone added any new backends for pulumi?
    w
    • 2
    • 1
  • g

    gifted-island-55702

    01/04/2019, 10:32 AM
    Hi! Is it possible to store a list as a configuration value? I would like to store a list of GCP API services for GCP project as a configuration entry (a list of strings).
    c
    w
    • 3
    • 10
  • f

    faint-motherboard-95438

    01/04/2019, 1:28 PM
    How am I supposed to keep consistent strings or data (ie. passwords) generated during components creation process (not coming from the config) ? If I generate something random, pulumi wants to change it every time I run an update, which is not what I want, I want to keep it during the stack lifetime or until destroyed otherwise.
    a
    w
    • 3
    • 5
  • g

    gifted-island-55702

    01/04/2019, 2:17 PM
    Hi. It seems that Pulumi Kubernetes provider doesn’t know it needs to recreate
    (Cluster)RoleBinding
    when a
    roleRef
    is changed - shall I open a github issue?
    kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> (k8s-auditors):
        error: Plan apply failed: 1 error occurred:
        
        * <http://RoleBinding.rbac.authorization.k8s.io|RoleBinding.rbac.authorization.k8s.io> "k8s-auditors" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"<http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>", Kind:"ClusterRole", Name:"view"}: cannot change roleRef
    a
    c
    • 3
    • 9
  • g

    gifted-island-55702

    01/04/2019, 2:58 PM
    Kubernetes provider: it seems that interfaces like
    core.v1.ContainerPort
    etc are not exported. Is there a change to change it? I would like to create my own
    ComponentResource
    class that would compose multiple k8s resources as a single ’deployment unit` and I would like to accept input options like a list of
    core.v1.ContainerPort
    or
    core.v1.EnvVar
    to customise the pod spec that will be part of that deployment. Otherwise I will need to create my own types to cover that which will be unnecessary boilerplate 😞
    i
    c
    • 3
    • 10
  • c

    chilly-photographer-60932

    01/05/2019, 2:26 AM
    With https://github.com/pulumi/pulumi-eks , when the master is upgraded , how can the nodes be upgraded?
    b
    • 2
    • 1
  • b

    busy-umbrella-36067

    01/05/2019, 4:45 PM
    Does https://github.com/pulumi/pulumi-eks do rolling upgrades of node AMI’s?
    w
    c
    • 3
    • 20
  • f

    faint-motherboard-95438

    01/07/2019, 1:35 PM
    I just got this warning (using
    @pulumi/gcp
    ) :
    warning: urn:pulumi:REDACTED::REDACTED::REDACTED:Cluster$gcp:container/nodePool:NodePool::REDACTED verification warning: "node_config.0.taint": [DEPRECATED] This field is in beta and will be removed from this provider. Use it in the the google-beta provider instead. See <https://terraform.io/docs/providers/google/provider_versions.html> for more details.
    The page says terraform provides 2 providers
    google
    and
    google-beta
    but I don’t see how to choose between them from a pulumi point of view, there’s only one class
    Provider
    without a
    beta
    option in
    @pulumi/gcp
    a
    w
    • 3
    • 3
  • p

    powerful-football-81694

    01/07/2019, 2:04 PM
    Hi folks. What's the right way to pass input parameters into a Pulumi program when executing it in a CI/CD context? I.e. values that should be used in one way or another by the Pulumi program in
    preview
    and
    update
    operations, but which are not config values stored in the stack but rather set and known by the release job on a per-release basis.
    m
    • 2
    • 11
  • h

    helpful-advantage-49286

    01/07/2019, 7:54 PM
    Hey all, looking at the kubernetes the prod way tutorial and curious if there is an ETA on the additional labs?
    m
    g
    c
    • 4
    • 53
  • b

    busy-umbrella-36067

    01/08/2019, 12:47 AM
    Seeing some strange behavior with tagging on the
    @pulumi/docker
    provider. I tried to write it up as best as I could: https://github.com/pulumi/pulumi-docker/issues/56 Not sure if its an actual bug, I may just be using the provider incorrectly
    w
    • 2
    • 1
  • c

    chilly-dusk-63796

    01/09/2019, 8:06 PM
    Join us for the AWS+Pulumi webinar on Feb 5th, 10AM PST https://blog.pulumi.com/upcoming-aws-pulumi-webinar-on-feb-5
  • e

    early-musician-41645

    01/09/2019, 8:25 PM
    What does one do when faced with this error when trying to
    pulumi refresh
    or
    pulumi destroy
    ?
    Do you want to perform this destroy? yes
    Destroying (tableau/online-sandbox-3-vpc-0d18addcc5815ae23):
    error: [409] Conflict: Another update is currently in progress.
    g
    c
    • 3
    • 3
  • e

    early-musician-41645

    01/09/2019, 8:31 PM
    Next question - it seems that I'm no longer authorized to modify an EKS cluster I created and I'm seeing errors like this:
    Do you want to perform this destroy? yes
    Destroying (tableau/online-vnext-10az):
    
         Type                                Name                              Status                  Info
         pulumi:pulumi:Stack                 eks-cluster-online-vnext-10az                             2 messages
     -   ├─ kubernetes:core:ConfigMap        kube-system/online-splunk-config  **deleting failed**     1 error
     -   └─ kubernetes:extensions:DaemonSet  kube-system/splunk-forwarder      **deleting failed**     1 error
    
    Diagnostics:
      kubernetes:core:ConfigMap (kube-system/online-splunk-config):
        error: Plan apply failed: Unauthorized
    
      pulumi:pulumi:Stack (eks-cluster-online-vnext-10az):
        warning: Cluster failed to report its version number; falling back to 1.9%!(EXTRA bool=false)
        warning: Cluster failed to report its version number; falling back to 1.9%!(EXTRA bool=false)
    
      kubernetes:extensions:DaemonSet (kube-system/splunk-forwarder):
        error: Plan apply failed: Unauthorized
    
    Permalink: <https://app.pulumi.com/tableau/online-vnext-10az/updates/82>
    error: update failed
    Any ideas on how I can modify/destroy it?
    c
    c
    • 3
    • 10
  • e

    early-musician-41645

    01/09/2019, 8:36 PM
    hmm... I think maybe I'm just not logging in to my org account properly. I have a personal account and an org account. How do I log in to get access to stacks in the org?
    c
    • 2
    • 8
  • h

    helpful-advantage-49286

    01/09/2019, 9:31 PM
    Is there a way to move a project from my personal account to the org?
    w
    • 2
    • 2
  • e

    early-musician-41645

    01/09/2019, 10:41 PM
    Anyone understand why I can't convert an ARN that I exported in one stack to a string that I read from config?
    let iamStack = new pulumi.StackReference(config.require("aws-iam-stack"));
    
    let clusterAutomationAccessRoleArn = iamStack.getOutput("clusterAutomationAccessRoleArn");
    if (config.get("clusterAutomationAccessRoleArn") != undefined) {
      clusterAutomationAccessRoleArn = config.require("clusterAutomationAccessRoleArn");
    }
    index.ts(71,3): error TS2322: Type 'string' is not assignable to type 'Output<any>'.
    The ARN is exported in another stack like this:
    export const clusterAutomationAccessRoleArn = automationRole.arn;
  • e

    early-musician-41645

    01/09/2019, 10:53 PM
    Perhaps another way of asking this is: how do I get the string value of an Output<any> ?
  • h

    helpful-advantage-49286

    01/09/2019, 10:53 PM
    .apply() is how I think
  • m

    microscopic-florist-22719

    01/09/2019, 10:54 PM
    that's correct
  • e

    early-musician-41645

    01/09/2019, 10:54 PM
    index.ts(65,38): error TS2554: Expected 1 arguments, but got 0.
  • m

    microscopic-florist-22719

    01/09/2019, 10:54 PM
    so the code can look like this:
  • m

    microscopic-florist-22719

    01/09/2019, 10:55 PM
    let iamStack = new pulumi.StackReference(config.require("aws-iam-stack"));
    
    let clusterAutomationAccessRoleArn: pulumi.Input<string> = <pulumi.Output<string>>iamStack.getOutput("clusterAutomationAccessRoleArn");
    if (config.get("clusterAutomationAccessRoleArn") != undefined) {
      clusterAutomationAccessRoleArn = config.require("clusterAutomationAccessRoleArn");
    }
  • e

    early-musician-41645

    01/09/2019, 10:57 PM
    that works! 👍 thanks
  • m

    microscopic-florist-22719

    01/09/2019, 10:57 PM
    np 🙂
  • a

    adventurous-kilobyte-12973

    01/09/2019, 11:27 PM
    I'm trying to implement a classic LB and load balancer listener through the pulumi/aws modules, and am having an issue identifying what needs to go under "defaultAction" for the listener's "listenerArgs". It appears to be mandatory within "listenerArgs".
  • a

    adventurous-kilobyte-12973

    01/09/2019, 11:27 PM
    https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/elasticloadbalancingv2/#ListenerArgs-defaultAction
Powered by Linen
Title
a

adventurous-kilobyte-12973

01/09/2019, 11:27 PM
https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/elasticloadbalancingv2/#ListenerArgs-defaultAction
View count: 1