vito

Commit Hooks: provenance for commits made through the engine

Builds on Workspace Git and Workspace Agents.

Design for letting modules observe the commits and pushes a workspace makes through the engine, and for linking those commits to the trace that made them. The motivating consumer is Entire, whose checkpoint model (a commit trailer naming a Git ref that holds the session transcript) fits Dagger's trace. The engine stays generic: it runs hooks and tells them where they are in the trace. It writes no trailer of its own.

vito

First-Class Interfaces and Unified IDs in DagQL

Table of Contents

• Problem
• Solution
• Unified ID Scalar
• First-Class Interfaces
• Fragment Support
• Interface-Implements-Interface

vito

vito

[
  {
    "context": "Editor && vim_mode == insert",
    "bindings": {
      "j k": "vim::NormalBefore",
      "k j": "vim::NormalBefore"
    }
  },
  {
    "context": "Editor && vim_mode == normal",

vito

package main

import (
	"context"
	"log"
	"os"

	"dagger.io/dagger"
)

vito

Keybase proof

I hereby claim:

• I am vito on github.
• I am alexsuraci (https://keybase.io/alexsuraci) on keybase.
• I have a public key whose fingerprint is 3B91 AB6B 7FB4 4314 C55F DCC9 AF0B C31D F64B EED7

To claim this, I am signing this object:

vito

jobs:
- name: print-some-creds
  plan:
  - task: leak
    config:
      platform: linux

      image_resource:
        type: registry-image
        source: {repository: concourse/unit}

vito

BRANCH=$(shell git rev-parse --abbrev-ref HEAD)

all: .git/HEAD

.git/HEAD: */proposal.md
	git add $?
	git commit -m "wip"
	git push origin HEAD:${BRANCH}-wip

vito

---
resource_types:
- name: gcs
  type: registry-image
  source: {repository: frodenas/gcs-resource}

resources:
- name: bosh-deployment
  type: git
  source:

vito

---
platform: linux

image_resource:
  type: docker-image
  source: {repository: gcr.io/kaniko-project/executor}

inputs:
- name: source