Phidata templates come pre-configured with Github Actions for CI/CD. We can
Whenever a PR is opened against the main
branch, a validate script runs that ensures
Checkout the .github/workflows/validate.yml
file for more information.
If you’re using Dockerhub for images, you can buld and push the images throug a Github Release. This action is defined in the .github/workflows/docker-images.yml
file.
DOCKERHUB_REPO
, DOCKERHUB_TOKEN
and DOCKERHUB_USERNAME
in your github repo. These variables are used by the action in .github/workflows/docker-images.yml
This workflow is configured to run when a release is created. Create a new release using:
Confirm the image name in the .github/workflows/docker-images.yml
file before running
You can also run the workflow using gh workflow run
If you’re using ECR for images, you can buld and push the images through a Github Release. This action is defined in the .github/workflows/ecr-images.yml
file and uses the new OpenID Connect (OIDC) approach to request the access token, without using IAM access keys.
We will follow this guide to create an IAM role which will be used by the github action.
Verify the information matches the screenshot below and Add provider
Add the AmazonEC2ContainerRegistryPowerUser
permission to this role.
Create the role with the name GithubActionsRole
.
Find the role GithubActionsRole
and copy the ARN.
llm
and jupyter-llm
which are built by the workflow.GithubActionsRole
ARN and ECR Repository.docker-images
workflow to NOT run on a releaseYou can also run the workflow using gh workflow run
Phidata templates come pre-configured with Github Actions for CI/CD. We can
Whenever a PR is opened against the main
branch, a validate script runs that ensures
Checkout the .github/workflows/validate.yml
file for more information.
If you’re using Dockerhub for images, you can buld and push the images throug a Github Release. This action is defined in the .github/workflows/docker-images.yml
file.
DOCKERHUB_REPO
, DOCKERHUB_TOKEN
and DOCKERHUB_USERNAME
in your github repo. These variables are used by the action in .github/workflows/docker-images.yml
This workflow is configured to run when a release is created. Create a new release using:
Confirm the image name in the .github/workflows/docker-images.yml
file before running
You can also run the workflow using gh workflow run
If you’re using ECR for images, you can buld and push the images through a Github Release. This action is defined in the .github/workflows/ecr-images.yml
file and uses the new OpenID Connect (OIDC) approach to request the access token, without using IAM access keys.
We will follow this guide to create an IAM role which will be used by the github action.
Verify the information matches the screenshot below and Add provider
Add the AmazonEC2ContainerRegistryPowerUser
permission to this role.
Create the role with the name GithubActionsRole
.
Find the role GithubActionsRole
and copy the ARN.
llm
and jupyter-llm
which are built by the workflow.GithubActionsRole
ARN and ECR Repository.docker-images
workflow to NOT run on a releaseYou can also run the workflow using gh workflow run