Skip to content

Commit

Permalink
Updated workflow
Browse files Browse the repository at this point in the history
  • Loading branch information
daku-de committed Jun 3, 2024
1 parent e2039af commit bfec0be
Show file tree
Hide file tree
Showing 3 changed files with 91 additions and 25 deletions.
25 changes: 12 additions & 13 deletions .github/workflows/customer.yml → .github/workflows/bank.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#
name: Create and publish a customer image
name: Create and publish a tax advisor image

# Configures this workflow to run every time a change is pushed to the branch called `release`.
# Configures this workflow to run every time a change is pushed to the branch called release.
on:
push:
branches:
Expand All @@ -16,7 +16,7 @@ env:
jobs:
build-and-push-image-consumer:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
# Sets the permissions granted to the GITHUB_TOKEN for the actions in this job.
permissions:
contents: read
packages: write
Expand All @@ -25,19 +25,19 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
# Uses the docker/login-action action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The id "meta" allows the output of this step to be referenced in a subsequent step. The images value provides the base name for the tags and labels.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-consumer
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-bank
tags: |
type=schedule
type=ref,event=branch
Expand All @@ -46,10 +46,10 @@ jobs:
# Change directory and copy Dockerfile
- name: Change directory and copy Dockerfile
working-directory: ./src
run: cp consumer.Dockerfile Dockerfile
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
run: cp bank.Dockerfile Dockerfile
# This step uses the docker/build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the context parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the docker/build-push-action repository.
# It uses the tags and labels parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
id: push
uses: docker/build-push-action@v4
Expand All @@ -63,7 +63,6 @@ jobs:
- name: Generate artifact attestation
uses: actions/attest-build-provenance@v1
with:
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}-consumer
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}-bank
subject-digest: ${{ steps.push.outputs.digest }}
push-to-registry: true

push-to-registry: true
23 changes: 11 additions & 12 deletions .github/workflows/provider.yml → .github/workflows/company.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#
name: Create and publish a provider image

# Configures this workflow to run every time a change is pushed to the branch called `release`.
# Configures this workflow to run every time a change is pushed to the branch called release.
on:
push:
branches:
Expand All @@ -16,7 +16,7 @@ env:
jobs:
build-and-push-image-provider:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
# Sets the permissions granted to the GITHUB_TOKEN for the actions in this job.
permissions:
contents: read
packages: write
Expand All @@ -25,19 +25,19 @@ jobs:
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
# Uses the docker/login-action action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The id "meta" allows the output of this step to be referenced in a subsequent step. The images value provides the base name for the tags and labels.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v4
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-provider
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-company
tags: |
type=schedule
type=ref,event=branch
Expand All @@ -46,10 +46,10 @@ jobs:
# Change directory and copy Dockerfile
- name: Change directory and copy Dockerfile
working-directory: ./src
run: cp provider.Dockerfile Dockerfile
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the `docker/build-push-action` repository.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
run: cp company.Dockerfile Dockerfile
# This step uses the docker/build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the context parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the docker/build-push-action repository.
# It uses the tags and labels parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
id: push
uses: docker/build-push-action@v4
Expand All @@ -63,7 +63,6 @@ jobs:
- name: Generate artifact attestation
uses: actions/attest-build-provenance@v1
with:
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}-provider
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}-company
subject-digest: ${{ steps.push.outputs.digest }}
push-to-registry: true

push-to-registry: true
68 changes: 68 additions & 0 deletions .github/workflows/tax_advisor.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
#
name: Create and publish a tax advisor image

# Configures this workflow to run every time a change is pushed to the branch called release.
on:
push:
branches:
- 'main'

# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}

# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
build-and-push-image-consumer:
runs-on: ubuntu-latest
# Sets the permissions granted to the GITHUB_TOKEN for the actions in this job.
permissions:
contents: read
packages: write
id-token: write
attestations: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Uses the docker/login-action action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The id "meta" allows the output of this step to be referenced in a subsequent step. The images value provides the base name for the tags and labels.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-tax_advisor
tags: |
type=schedule
type=ref,event=branch
type=semver,pattern={{version}}
type=sha
# Change directory and copy Dockerfile
- name: Change directory and copy Dockerfile
working-directory: ./src
run: cp tax_advisor.Dockerfile Dockerfile
# This step uses the docker/build-push-action action to build the image, based on your repository's Dockerfile. If the build succeeds, it pushes the image to GitHub Packages.
# It uses the context parameter to define the build's context as the set of files located in the specified path. For more information, see "[Usage](https://github.com/docker/build-push-action#usage)" in the README of the docker/build-push-action repository.
# It uses the tags and labels parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
id: push
uses: docker/build-push-action@v4
with:
context: ./src
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
platforms: linux/amd64
# This step generates an artifact attestation for the image, which is an unforgeable statement about where and how it was built. It increases supply chain security for people who consume the image. For more information, see "[AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds)."
- name: Generate artifact attestation
uses: actions/attest-build-provenance@v1
with:
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}-tax_advisor
subject-digest: ${{ steps.push.outputs.digest }}
push-to-registry: true

0 comments on commit bfec0be

Please sign in to comment.