Skip to content

feat: layers-from input adds the one layer of your own images - #160

Merged
cnuss merged 1 commit into
githubfrom
feat/layers-from-input
Oct 25, 2026
Merged

cnuss merged 1 commit into
githubfrom
feat/layers-from-input

Conversation

@cnuss

@cnuss cnuss commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Task 5 of #158. The Action's new layers-from: input is passed to rowdy as ROWDY_LAYERS_FROM, one image per line. It needs rowdy 0.1.0-beta.20261025062659.83573b4 (#159) or later, which the Action's npx @scaffoldly/rowdy@beta now resolves to.

- uses: scaffoldly/rowdy@github
  with:
    cloud: aws
    compute: lambda
    image: ghcr.io/owner/app@sha256:...
    layers-from: |
      ghcr.io/tunnel-pizza/tunneld:latest

Each image must be public and built like rowdy's final stage (FROM scratch, one COPY, ENTRYPOINT), or the deploy fails before anything is copied. Its one layer goes on before rowdy's. Rules: Your own layers.

README: a new inputs row. Prettier re-padded the table, since layers-from is the longest input name.

Checked: action.yml parses, the layers-from input exists, and the deploy step's env maps ROWDY_LAYERS_FROM: ${{ inputs.layers-from }}. The end-to-end deploy with tunneld, through CI, is still to do once this is merged.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

Passed to rowdy as ROWDY_LAYERS_FROM, one image per line. Each must be public and built like rowdy's final stage (FROM scratch, one COPY), or the deploy fails.

Refs #158

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant