github-run-changesets-testing

Overview

This repository automates InProd changeset deployments using GitHub Actions. When changesets are pushed to the repository, the workflow automatically deploys them to the appropriate environment based on the branch name.

How It Works

The deployment workflow is triggered whenever changes are pushed to the changesets/ directory on the following branches:

• Dev → Deploys to Development environment
• UAT → Deploys to UAT environment
• Prod → Deploys to Production environment

The branch name is used directly as the environment parameter passed to the InProd deployment action.

Changesets

Changesets are defined as YAML files in the changesets/ directory. Each changeset describes the infrastructure or configuration changes to apply.

Example Structure

# changesets/datatable.yaml
# Define your changeset configuration here

Workflow

The GitHub Actions workflow (.github/workflows/deploy-changesets.yml) performs the following steps:

1. Checks out the repository code
2. Extracts the branch name (Dev, UAT, or Prod)
3. Deploys all changesets matching changesets/*.yaml to the corresponding environment

Requirements

• Valid INPROD_API_KEY stored as a GitHub secret
• Changesets defined in YAML format in the changesets/ directory End to end functional testing and demo for github-run-changesets

Overview

This repository demonstrates the integration of InProd GitHub Run Changesets action for automating Genesys Cloud configuration deployments.

Setup

1. Repository Structure

.
├── .github/
│   └── workflows/
│       └── deploy-changesets.yml  # GitHub Actions workflow
├── changesets/
│   └── datatable.yaml            # InProd changeset file
└── README.md

2. Configuration

The repository is configured to automatically deploy changesets when changes are pushed to specific branches:

• dev → Development environment
• uat → UAT environment
• main → Production environment

3. Required Secrets

Before using this action, you need to configure the following GitHub secret:

• INPROD_API_KEY: Your InProd API key (configured in repository or organization secrets)

4. Environment Variables

The workflow uses the following environment variables:

• INPROD_BASE_URL: https://gray.dev.inprod.io/
• INPROD_API_KEY: Retrieved from GitHub Secrets

Usage

1. Add or modify changeset files in the changesets/ directory
2. Commit and push to one of the monitored branches (dev, uat, or main)
3. The GitHub Action will automatically:
   • Validate the changeset
   • Deploy to the appropriate environment based on the branch
   • Report the results

Example Changeset

See changesets/datatable.yaml for an example of creating a Genesys Cloud Architect Flow Datatable.

Workflow Triggers

The workflow is triggered on:

• Push to dev, uat, or main branches
• Only when files in the changesets/** directory are modified

Learn More

• InProd GitHub Run Changesets Action
• InProd Platform Documentation