Skip to content

[Backend.Tests] Use Constraint Model in Helper, Models, and Services tests #1883

[Backend.Tests] Use Constraint Model in Helper, Models, and Services tests

[Backend.Tests] Use Constraint Model in Helper, Models, and Services tests #1883

Workflow file for this run

name: database
on:
pull_request:
branches: [master]
permissions: # added using https://github.com/step-security/secure-workflows
contents: read
jobs:
docker_build:
if: ${{ github.event.type }} == "PullRequest"
runs-on: ubuntu-latest
steps:
# See https://docs.stepsecurity.io/harden-runner/getting-started/ for instructions on
# configuring harden-runner and identifying allowed endpoints.
- name: Harden Runner
uses: step-security/harden-runner@cba0d00b1fc9a034e1e642ea0f1103c282990604 # v2.5.0
with:
disable-sudo: true
egress-policy: block
allowed-endpoints: >
auth.docker.io:443
github.com:443
production.cloudflare.docker.com:443
registry-1.docker.io:443
# For subfolders, currently a full checkout is required.
# See: https://github.com/marketplace/actions/build-and-push-docker-images#path-context
- uses: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9 # v3.5.3
with:
fetch-depth: 0
- name: Build database image
run: |
deploy/scripts/build.py --components database
shell: bash
- name: Image digest
run: |
docker image inspect combine_database:latest -f '{{json .Id}}'
shell: bash