GitHub Actions gives you the flexibility to build automated software development workflows. With GitHub Actions for Okteto you can create workflows to build, deploy and update your applications in Okteto. Follow this tutorial for a full preview environment configuration sample.
Try Okteto for free for 30 days, no credit card required. Start your 30-day trial now!
You can use this action to create a preview environment in Okteto as part of your automated development workflow.
Required The name of the Okteto preview environment to create.
The length of time to wait for completion. Values should contain a corresponding time unit e.g. 1s, 2m, 3h. If not specified it will use 5m
.
A list of variables to be used by the pipeline. If several variables are present, they should be separated by commas e.g. VAR1=VAL1,VAR2=VAL2,VAR3=VAL3.
Relative path within the repository to the manifest file (default to okteto-pipeline.yaml or .okteto/okteto-pipeline.yaml).
The branch to use for the preview environment (defaults to the branch that triggered the action).
Log level used. Supported values are: debug
, info
, warn
, error
. (defaults to warn
)
If the GITHUB_TOKEN
environment variable is set, the action will share the URL of the preview environment with the pull request that triggered the action.
This example runs the context action and then creates a preview environment.
# File: .github/workflows/workflow.yml
on: [push]
name: example
concurrency:
# more info here: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: false
jobs:
devflow:
runs-on: ubuntu-latest
steps:
- name: Context
uses: okteto/context@latest
with:
url: https://okteto.example.com
token: ${{ secrets.OKTETO_TOKEN }}
- name: "Deploy the preview environment"
uses: okteto/deploy-preview@latest
with:
name: dev-previews
You can specify a custom certificate authority or a self-signed certificate by setting the OKTETO_CA_CERT
environment variable. When this variable is set, the action will install the certificate in the container, and then execute the action.
Use this option if you're using a private Certificate Authority or a self-signed certificate in your Okteto SH instance. We recommend that you store the certificate as an encrypted secret, and that you define the environment variable for the entire job, instead of doing it on every step.
# File: .github/workflows/workflow.yml
on: [push]
name: example
concurrency:
# more info here: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: false
jobs:
devflow:
runs-on: ubuntu-latest
env:
OKTETO_CA_CERT: ${{ secrets.OKTETO_CA_CERT }}
steps:
- name: Context
uses: okteto/context@latest
with:
url: https://okteto.example.com
token: ${{ secrets.OKTETO_TOKEN }}
- name: "Deploy the preview environment"
uses: okteto/deploy-preview@latest
with:
name: dev-previews
timeout: 15m