Conversation
- Implement initial release of the OpEx Dashboard Generate action - Include scripts for detecting changes, generating Terraform, and creating pull requests - Add comprehensive README and CHANGELOG for usage and features - Ensure security best practices with fork protection and proper variable quoting
…board Generate action
…and security validations - Add parallel processing for dashboard generation - Implement npm package caching to speed up runs - Introduce dry run support for previewing changes - Validate input patterns to prevent injection attacks - Modify commit behavior to include only Terraform files
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…e for OpEx dashboard action
…o chores/opex-action
… instructions for OpEx Dashboard Generate action
… and functionality - Updated README.md to enhance usage examples and migration instructions. - Modified action.yaml to support multiple config patterns and removed unnecessary inputs. - Replaced create-pr.sh with direct PR handling in the workflow. - Enhanced detect-changes.sh to support multiple config patterns and improved change detection logic. - Introduced extract-directories.sh for better management of generated Terraform files. - Added opex-dashboard-deploy.yaml for streamlined deployment processes.
🦋 Changeset detectedLatest commit: cbf87a2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
… improved clarity and maintainability
gunzip
changed the title
…d clarity and functionality
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces a new reusable workflow and composite action for automatically detecting, generating, and deploying OpEx dashboards from OpenAPI specifications to Azure infrastructure. The solution provides smart change detection, parallel processing, and integration with existing Terraform deployment workflows.
Changes:
- Added comprehensive documentation for the OpEx Dashboard deployment workflow with usage examples, architecture details, and migration guide
- Created a composite action for detecting configuration changes and generating Terraform code from dashboard configs
- Implemented a reusable workflow that orchestrates generation and parallel deployment using matrix strategy
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
apps/website/docs/pipelines/opex-dashboard.md |
Comprehensive documentation covering features, usage, architecture, security, and migration |
apps/website/docs/pipelines/index.md |
Added OpEx Dashboard link to pipelines index |
actions/opex-dashboard-generate/package.json |
Package metadata for the new composite action |
actions/opex-dashboard-generate/generate-terraform.sh |
Script to generate Terraform files from dashboard configs using @pagopa/opex-dashboard |
actions/opex-dashboard-generate/extract-directories.sh |
Script to extract directories containing generated Terraform and format for matrix deployment |
actions/opex-dashboard-generate/detect-changes.sh |
Script to detect modified config files and referenced OpenAPI specs |
actions/opex-dashboard-generate/action.yaml |
Composite action manifest defining inputs, outputs, and orchestration steps |
actions/opex-dashboard-generate/README.md |
Action documentation with quick examples and architecture overview |
.github/workflows/opex-dashboard-deploy.yaml |
Reusable workflow for parallel dashboard generation and deployment |
.changeset/new-opex-dashboard-generate-action.md |
Changeset file for version bump |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…and dashboard version
…t input and standardize Node.js setup; enhance Terraform generation script to support multiple package managers
…; update documentation to reflect expected config file structure
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…te documentation for backend variable file
…move outdated sections and enhance feature descriptions
…nto chores/opex-workflow
…ackages; improve documentation prerequisites for clarity
Krusty93
reviewed
Feb 19, 2026
Krusty93
reviewed
Feb 19, 2026
Krusty93
reviewed
Feb 19, 2026
Krusty93
reviewed
Feb 19, 2026
…pdate action reference; enhance deployment conditions for apply job
lucacavallaro
approved these changes
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enhance the OpEx Dashboard action by improving documentation, supporting multiple config patterns, and streamlining deployment processes. Introduce new scripts for better management of generated Terraform files and optimize change detection logic.