Nomad Plugin - allow specification of an hcl file about waypoint HOT 11 CLOSED

and as an elevated version of this, levant integration, so that we can pass variables to the nomad script

from waypoint.

@orenmazor
exec plugin has issues, documetation, but here one example.

### waypoint.hcl
project = "example-python"
app "example-python" {
  labels = {
    "service" = "example-python",
    "env" = "dev"
  }

  build {
    use "docker" {}
    registry {
      use "docker" {
        image = "python-example"
        tag = "1"
        local = true
      }
    }
  }

  deploy {
    use "exec" {
        command = ["nomad","run","job.hcl"]
    }
  }
}
### job.hcl
job "example" {
  datacenters = ["dc1"]

  group "demo" {
    network {
      port "web" {
        to = 8080
      }
    }

    task "python" {
      driver = "docker"
      config {
        image = "python-example:1"
        ports = ["web"]
      }

      resources {
        cpu    = 500
        memory = 256
      }
    }
  }
}

and you right, is not ideal, but works, I don't recommend for production envs, but for dev or demo is ok

from waypoint.

I ran into similar issues with the limitations of the nomad plugin and ended up creating a levant plugin. I'll link to it here in case anyone else would find it helpful: https://github.com/MarilynFranklin/waypoint-plugin-levant

from waypoint.

I can't help but assume somebody is out there at this very moment hacking a levant plugin, and I wish I could buy that person a beer

from waypoint.

you can use exec plugin to deploy the job file

from waypoint.

@kaykelins I'm having a hard time visualizing this but I'm super interested. can you post a small example? in my mind the exec plugin is for one-off tasks and not for CD

from waypoint.

That'd get us over the initial hurdle for testing, though I'm guessing that things like job deployment status aren't supported (the main use case for us). Levant might be a better choice for us for now.

from waypoint.

just a followup: this exec+levant approach has turned into the way I deploy 3 different stacks now. A++

from waypoint.

Fixed by #1299, will be in 0.4

from waypoint.

@orenmazor exec plugin has issues, documetation, but here one example.

### waypoint.hcl
project = "example-python"
app "example-python" {
  labels = {
    "service" = "example-python",
    "env" = "dev"
  }

  build {
    use "docker" {}
    registry {
      use "docker" {
        image = "python-example"
        tag = "1"
        local = true
      }
    }
  }

  deploy {
    use "exec" {
        command = ["nomad","run","job.hcl"]
    }
  }
}
### job.hcl
job "example" {
  datacenters = ["dc1"]

  group "demo" {
    network {
      port "web" {
        to = 8080
      }
    }

    task "python" {
      driver = "docker"
      config {
        image = "python-example:1"
        ports = ["web"]
      }

      resources {
        cpu    = 500
        memory = 256
      }
    }
  }
}

and you right, is not ideal, but works, I don't recommend for production envs, but for dev or demo is ok

But how can I pass the tag= gitrefpretty() to nomad.hcl?

from waypoint.

I have problem to build ->

✓ Running build v11
✓ Building Docker image with kaniko...
❌ Testing registry and uploading entrypoint layer
! error setting up entrypoint layer to host

from waypoint.