push-to-prodvana Github Action

This action simplifies pushing a new container image to a Prodvana service.

Requirements

• pvnctl present in the CI environment
  • We recommend using init-pvnctl-action to handle installation and authentication initialization

Usage

Inputs

Input	Default	Description
app	(required)	Name of the Application containing the service being updated
service	(required)	Name of the Service to update
docker_image	(optional)	Comma separated key-value pairs of '<program_name>=<docker_image>'. if the service has a single program, you can pass the single <docker_image> directly
parameters	(optional)	Comma separated key-value pairs of '<parameter_name>='.
wait_channels	(optional)	Comma separated list of the names of Release Channels to wait for before considering this push complete
auth_context	default	pvnctl auth context to use. If you're using this action with init-pvnctl, leave as the default

Basic Usage

steps:
  # pvnctl must be installed in your Action environment for push-to-prodvana
  - uses: prodvana/[email protected]
    with:
      org: my-org
      api_token: ${{ secrets.YOUR_PRODVANA_API_TOKEN }}

  - uses: prodvana/[email protected]
    with:
      app: my-application
      service: my-service
      parameters: serviceImage=index.dockerhub.com/python:3.11.4-slim-bookworm
      wait_channels: staging # wait for the staging release channel to complete before considering this complete

  # Deprecated image update mechanism (use parameters instead)
  - uses: prodvana/[email protected]
    with:
      app: my-application
      service: my-deprecated-service
      docker_image: index.dockerhub.com/python:3.11.4-slim-bookworm
      wait_channels: staging # wait for the staging release channel to complete before considering this complete