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

    creamy-potato-29402

    09/10/2018, 5:29 AM
    Can you give that a shot instead and see what the result is? If it fails I’ll help you debug it. 🙂
    g
    • 2
    • 3
  • g

    glamorous-printer-66548

    09/10/2018, 6:30 AM
    @creamy-potato-29402 log output from pulumi
    -.sh
  • c

    creamy-potato-29402

    09/10/2018, 6:58 AM
    @glamorous-printer-66548 great!
  • c

    creamy-potato-29402

    09/10/2018, 6:58 AM
    Also terrible!
  • c

    creamy-potato-29402

    09/10/2018, 6:58 AM
    @white-balloon-205 and I will spend some time chatting about this tomorrow and I’ll try to get a fix out ASAP — hopefully before the PR ships.
  • g

    glamorous-printer-66548

    09/10/2018, 8:26 AM
    @creamy-potato-29402 I have another observation / request. As you can see above I’m injecting a short-lived access token into the docker build command (via
    password: execSync('gcloud auth print-access-token').toString('utf8'))
    ). This access token changes on every
    pulumi up
    invocation and because of this pulumi shows the resource as updated on every invocation. I’m not sure if it’s a good design decision that pulumi considers the password / access_token part of the permanent state / checkpoint of the resource since it’s more or less a secret that it just needed to create the resource but not a crucial part of the resource itself (i.e. unlike a password of a database resource). Also for GCR there is no classic notion of a long lived username / password (see https://cloud.google.com/container-registry/docs/advanced-authentication) . I think the easiest / quick-win for me would be if you allow to disable authentication (i.e. skip
    docker login
    ) since my local docker is already authenticated automatically via gcloud which is registered as docker credential helper (see also https://cloud.google.com/sdk/gcloud/reference/auth/configure-docker).
    c
    • 2
    • 4
  • a

    able-megabyte-54679

    09/10/2018, 2:56 PM
    hey, guys. Is there any instructions on how to go from the examples approach of having all pulumi files in the root of the directory to placing them in a .pulumi folder? Maybe a flag that should be passed on when creating the stack, updating and so on?
    s
    • 2
    • 4
  • w

    white-balloon-205

    09/11/2018, 4:26 AM
    Only indirectly related to Pulumi - but really nice post from @tall-librarian-49374 on the front page of HN right now. https://news.ycombinator.com/item?id=17949694 https://mikhail.io/2018/08/serverless-cold-start-war/
  • f

    faint-application-2746

    09/11/2018, 9:04 AM
    this reminds me of GraalVM promise of fixing cold start on Java lambda bits
  • a

    adventurous-jordan-10043

    09/11/2018, 12:42 PM
    https://github.com/pulumi/examples/tree/master/aws-ts-eks is not working for me on pulumi 0.15.1 and node 10. Error is :
    error: Error: invocation of aws:index/getAmi:getAmi returned an error: invoking aws:index/getAmi:getAmi: Your query returned no results. Please change your search criteria and try again.
  • a

    adventurous-jordan-10043

    09/11/2018, 12:59 PM
    ok quick fix PR : https://github.com/pulumi/eks/pull/4
  • t

    tall-librarian-49374

    09/11/2018, 2:08 PM
    Thanks @white-balloon-205 for posting! It's more directly related to Pulumi since all AWS and GCP code for testing was done with Pulumi. I've been firing 100x of lambdas with a simple javascript array, very handy!
    💯 1
    🎉 4
    ⚡ 1
  • s

    stocky-spoon-28903

    09/11/2018, 2:30 PM
    Interesting read @tall-librarian-49374
  • f

    fresh-umbrella-15520

    09/11/2018, 10:06 PM
    Hi, I am curious if the kubernetes module now supports specifying a namespace for helm charts? I tested with the following:
    index_ts.ts
  • f

    fresh-umbrella-15520

    09/11/2018, 10:06 PM
    package_json.js
  • f

    fresh-umbrella-15520

    09/11/2018, 10:07 PM
    Am I calling the namespace incorrectly?
  • m

    microscopic-florist-22719

    09/11/2018, 10:25 PM
    It does support a
    namespace
    argument, but it is currently up to the Helm chart to respect that setting. Providing a
    namespace
    argument boils down to passing the
    --namespace
    flag to
    helm
    , which sets the
    .Release.Namespace
    variable when executing the chart's templates. The chart author is responsible for adding the appropriate uses of the
    .Release.Namespace
    variable.
  • m

    microscopic-florist-22719

    09/11/2018, 10:25 PM
    Does that make sense?
  • f

    fresh-umbrella-15520

    09/11/2018, 10:26 PM
    interesting, as I can run the chart manually with that flag and have it go to
    kube-tools
    m
    c
    • 3
    • 29
  • g

    glamorous-printer-66548

    09/12/2018, 2:58 AM
    hey folks, this is a bit OT: Do you know a good CI/CD system / technology / service which allows using a real programming language instead of YAML for expressing complex pipelines?? I just know of Jenkins Pipeline (Groovy), TeamCity (Kotlin Script) and Airflow (Python), but all of these have significant maintenance burden. I’d like to have something a la CircleCI but without YAML.
    c
    • 2
    • 3
  • c

    creamy-potato-29402

    09/12/2018, 3:01 AM
    -.ts
  • c

    creamy-potato-29402

    09/12/2018, 3:02 AM
    Threads don’t do snippets I guess. Anyway:
    Here is the core of the example — ~15 lines of code that incrementally roll out a staged deployment, gated on Prometheus metrics.
    From here: https://github.com/pulumi/examples/tree/master/kubernetes-ts-staged-rollout-with-prometheus
  • c

    creamy-potato-29402

    09/12/2018, 3:03 AM
    In time, I’m hoping that we will have enough tools that you don’t need to use, e.g., Jenkins.
  • c

    creamy-potato-29402

    09/12/2018, 3:03 AM
    If you want to do only Kubernetes, Argo is worth a shot.
  • g

    glamorous-printer-66548

    09/12/2018, 3:10 AM
    Hmm, I’m not sure if that’s what I had in mind, but interesting nevertheless. What happens when the P90 latency is > 100,000 microsends in your example? Does it reject the promise returned by
    util.checkHttpLatency
    and in turn aborts the deployment?
  • c

    creamy-potato-29402

    09/12/2018, 3:10 AM
    Yeah.
  • g

    glamorous-printer-66548

    09/12/2018, 3:10 AM
    I see, good to know
  • g

    glamorous-printer-66548

    09/12/2018, 3:12 AM
    Yeah, what I’m looking for is basically a pipeline execution environment which executes arbitrary scripts as steps and has gates (incl. manual approval gates) in between. I expect many pipeline steps to just invoke pulumi, but I don’t see pulumi making a CI/CD platform completely obsolete as of now.
  • c

    creamy-potato-29402

    09/12/2018, 3:12 AM
    yeah, me neither.
  • g

    glamorous-printer-66548

    09/12/2018, 3:13 AM
    We btw already use argo, but only for some ML training, not CI/CD. argo-ci seems too immature as of now (also has no gated approvals) and argo-cd is very opinionated and limited to k8s deployments (i.e. i cannot deploy some non-k8s stuff with it).
Powered by Linen
Title
g

glamorous-printer-66548

09/12/2018, 3:13 AM
We btw already use argo, but only for some ML training, not CI/CD. argo-ci seems too immature as of now (also has no gated approvals) and argo-cd is very opinionated and limited to k8s deployments (i.e. i cannot deploy some non-k8s stuff with it).
View count: 1