datawire/forge

we're migrating to Slack https://bit.ly/2s8s3RQ

datawirebot

@datawirebot

<Andrei> Is it possible somehow to ovveride a defined variable in the service.yaml ?

datawirebot

@datawirebot

<peter.kim> hi

<peter.kim> new error - everyone is having issues

Error response from daemon: Get https://dev1-registry-docker-registry.aws.aurotfp.com:5000/v2/: net/http: TLS handshake timeout

nothing specifically changed on anyone's system

<peter.kim> any quick thougghts?

<peter.kim> ok looks like one of the nodes under my loadbalancer isn't playing nice

datawirebot

@datawirebot

<onzyone> Hello there, is there a way that we can pass in OS environment variables to the service.yaml file?

<onzyone> ```containers:

dockerfile: Dockerfile
args:
ARG_NPM_AUTH_TOKEN: "get os env var"
ARG_NPM_PASSWORD: "get os env var"
ARG_NPM_USERNAME: "get os env var"
ARG_REGISTRY_URL: "get os env var"```

datawirebot

@datawirebot

<onzyone> nvm ... found the docs

<onzyone> https://forge.sh/docs/reference/environments

datawirebot

@datawirebot

This message was deleted

datawirebot

@datawirebot

<Wallett> Hi, I've been playing with Forge over the last few days, really like what you've put together here! I'm looking at integrating Forge into my Jenkins setup and was wondering if you had a tips for generating the forge.yaml file? I don't want to store any secrets in GitHub so figured it's best to inject the registry password via an environment variable

<Wallett> As the moment I'm rather crudely generating a forge.yaml file and replacing the password with sed

<Wallett> ``` #!/bin/bash

curl https://s3.amazonaws.com/datawire-static-files/forge/$(curl https://s3.amazonaws.com/datawire-static-files/forge/latest.url)/forge -o ./forge
chmod a+x ./forge

REGISTRY_PASSWORD=$1

sed -e "s/\${registry.password}/$REGISTRY_PASSWORD/" forge.template.yaml > forge.yaml ```

datawirebot

@datawirebot

<Andrei> hi @Wallett

I successfully integrated forge in my jenkins setup.
I just inject forge.yaml during build setup.

here is a sample of pipeline:

...
    environment {
        forge_file=credentials('b9367523-460b-4e75-9b11-2ebde74685ae')
            }
...
stages{
stage('upload forge config') {
            steps{
                sh 'cat $forge_file > forge.yaml'
            }
        }
...

<Wallett> Thanks @Andrei makes sense 👍 I'm new to jenkins so didn't think to use credentials for this

<Andrei> @Wallett
I generated forge.yaml un my workstation. And copied it to jenkins as a secret file.
This file is injected in workspace during build

datawirebot

@datawirebot

<Andrei> *
It is possible to ask forge to use a custom ~/.kube/config ?

datawirebot

@datawirebot

<rdl> Hi @Wallett you should be able to avoid using credentials at all in your forge.yaml file if you just have your registry credentials stored and you can docker login

<rdl> forge just invokes kubectl so if you use something like kubectx it should work

<Wallett> ah cool, so I can just omit the registry password config from the forge.yaml file, I'll give it a go!

datawirebot

@datawirebot

<rdl> @Wallett here's my forge.yaml: https://github.com/datawire/bb-kubecon/blob/master/forge.yaml

datawirebot

@datawirebot

This message was deleted

datawirebot

@datawirebot

<paul> Hi - I had a forge question about profiles. Can use profiles not defined in our service.yaml or dynamically allocate a profile? We want to have each developer have their own profile (so they can easily bring up and tear down their services) - we also want add new profiles without modifying our service.yaml. Is there a way to do this?

datawirebot

@datawirebot

<petejohanson> Reading through https://github.com/datawire/forge/blob/e78a297425d402ce5a87c1d193915c182706f06f/forge/docker.py am I following correctly that forge doesn't support configured credsStores?

<petejohanson> I'd really rather not keep my plain text stuff in ~/.docker/config.json just to use a tool like forge...

datawirebot

@datawirebot

<petejohanson> @rdl ^ Any insight?

datawirebot

@datawirebot

<jeet.jagasia> Just learned about Forge - I see the projects are 2 years old https://github.com/datawire/hello-forge and https://github.com/datawire/hello-forge-network.git . Is Forge project still active? I read that one doesnt need to craft yaml files, but the project has them in k8s directory. Whats the scoop?

datawirebot

@datawirebot

<Negan Grimes> "Normally, if you want to get a service running in Kubernetes, you need to build a Docker image, push the image to a Docker registry, write some Kubernetes YAML, and run kubectl to get the service running.

With Forge, the deploy command will take care of everything you need to get the service running. Try it now: "

For me, the appeal of forge is having a single deployment.yaml file with profiles, so in a test environment, you might have different resource limits or routing paths, while for a canary deployment you might only want to route a small amount of traffic to the deployment, and for production you might have another profile

<Negan Grimes> instead of having 3 kubernetes deployment.yaml files, you only need 1 and you can deploy it with the profile name which will fill out all the "placeholders" in your deployment.yaml file

<Negan Grimes> I didn't really need all the other features, So I personally created my own version in Go for this

datawirebot

@datawirebot

This message was deleted

datawirebot

@datawirebot

<peter.kim> hey - any chance datawire would upgrade the jinja templater to use ansible jinja? we would love to see the toyaml filter....

datawirebot

@datawirebot

<jeet.jagasia> @Negan Grimes Are you part of the Forge team? It wasnt clear based on your response. Can you share what you have created and point me in the right direction on how you are doing it?

datawirebot

@datawirebot

<Negan Grimes> Hi, sorry for the late response. I am not part of the forge team, I just liked the idea of it and created my own tool in Go (I like having a single static binary)

datawirebot

@datawirebot

<blake> trying to hack on forge, read https://github.com/datawire/forge/blob/master/DEVELOPING.md and got ./dev.sh build to work ... but now what I have is a docker container with my modified forge ... how can I actually use it (distribute it to my team?)

<blake> that is, how can I extract a forge executable from the build container (or am I going about this the wrong way?)

datawirebot

@datawirebot

This message was deleted

datawirebot

@datawirebot

<jeet.jagasia> ok, Can you share what you created and how its different?

datawirebot

@datawirebot

<devon> hey all, is there a way to set "top-level" profile settings in forge.yaml?

<devon> mainly, there's shared settings between service+environment mappings that I want to keep between services

datawirebot

@datawirebot

<plombardi> @devon use env files and source them before invoking forge, that might get you close to your goal?

datawirebot

@datawirebot

<peter.kim> hey - there was a command to render service.yaml or show the environment after rendering the manifests. can someone please refresh my memory?

datawirebot

@datawirebot

<Andrei> Is it possible to define Dockerfile args in the same way as profile. I would like to use one build argument for prod and another one for staging. Is there a way to do it?

yangruizeng

@yangruizeng

Is forge rebuild configuration based on the last image build?

datawirebot

@datawirebot

<brentbaum> Hello! Is there an easy way to print out the profile settings that were used after a forge deploy succeeds?

Background: I'm trying to construct and print the URL of a deployment (using Ambassador + custom endpoint) so that we can copy and paste the URL to be used elsewhere. Maybe there's a way to get this OOTB w/ Ambassador and I should be asking there, but I couldn't find it.