Add configurable CONFIG_PATH input to docker artifact workflows

[Copilot]

Workflows hardcoded ./deploy/build/config.json path, preventing use of alternative configurations for different build scenarios.

Changes

• Added config_path input parameter (default: ./deploy/build/config.json) to:
  • build-docker-artifacts.yml
  • build-docker-artifacts-trigger-push.yml
• Updated config loading in validation steps and JavaScript actions to use input parameter
• Used path.resolve() for absolute path resolution in require() statements
• Propagated config_path through nested workflow calls
• Automatically infer config directory from config_path: The directory containing the config file is extracted using path.dirname() and used for all related paths including:
  • Hooks directory for test scripts
  • Flavor directories for components
  • _base folder for shared configuration files

Usage

jobs:
  build:
    uses: datavisyn/github-workflows/.github/workflows/build-docker-artifacts.yml@main
    with:
      config_path: ./deploy/build/config.staging.json

Default behavior unchanged—omit parameter to use ./deploy/build/config.json. All paths relative to the config file (hooks, flavors, _base) are automatically resolved based on the config file location.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add CONFIG_PATH input for all workflows that use the ./deploy/build/config.json</issue_title>
<issue_description>By default, the ./deploy/build/config.json is perfectly fine, but sometimes we want to override the CONFIG_PATH as workflow input to run a separate configuration. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add CONFIG_PATH input for all workflows that use the ./deploy/build/config.json #262

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.