Skip to content

Add vault unlock

Add vault unlock #14

Workflow file for this run

### This file provides a template for creating a GitHub Actions Workflow,
### that implements ci for a Docker Image.
name: Docker CI
on:
push:
branches:
- $default-branch
- develop
# Build then a new version is tagged
tags:
- '*.*.*'
pull_request:
branches:
- $default-branch
- develop
schedule:
# Build every night at 1am
- cron: '0 1 * * *'
jobs:
build:
# This workflow defines how a maven package is built, tested and published.
# Visit: https://github.com/samply/github-workflows/blob/develop/.github/workflows/maven-ci.yml, for more information
uses: samply/github-workflows/.github/workflows/docker-ci.yml@main

Check failure on line 25 in .github/workflows/main.yml

View workflow run for this annotation

GitHub Actions / Docker CI

Invalid workflow file

The workflow is not valid. .github/workflows/main.yml (Line: 25, Col: 11): Input push-to is required, but not provided while calling.
with:
# The Docker Hub Repository you want eventually push to, e.g samply/share-client
image-name: "samply/bridgehead-vaultfetcher"
# Define special prefixes for docker tags. They will prefix each images tag.
# image-tag-prefix: "foo"
# Define the build context of your image, typically default '.' will be enough
# build-context: '.'
# Define the Dockerfile of your image, typically default './Dockerfile' will be enough
# build-file: './Dockerfile'
# A list of build arguments, passed to the docker build
# build-args: |
# foo: bar
# Define the target platforms of the docker build (default "linux/amd64,linux/arm64/v8")
# build-platforms: "linux/amd64,linux/arm64/v8"
# If your actions generate an artifact in a previous build step, you can tell this workflow to download it
# artifact-name: '' # the default '' doesn't try to download an artifact
# This passes the secrets from calling workflow to the called workflow
secrets:
DOCKERHUB_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}
DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}