Skip to content

Conversation

@happz
Copy link
Contributor

@happz happz commented Jan 9, 2026

Pull Request Checklist

  • implement the feature
  • write the documentation
  • extend the test coverage
  • include a release note

happz added 2 commits January 9, 2026 10:14
This was a major drawback when using envvars to populate or change
phases' configuration: plugin-specific envvars had no effect unless the
plugin was invoked via command line. This was caused by Click consuming
them, and without mentioning the plugin on command line, Click was not
invoked, therefore nothing consumed said envvars.

The patch adds one more pass into the application of CLI invocations
where we collect all these envvars, and then we use Click to process
them. The produced values are then added into raw step data.

We do not use custom parsers or type casting, we identify the plugin in
question from the envvar name, and use its Click command and its
parameters to perform the necessary steps for us. This should be
equivalent to what Click does when crunching the command line.
@happz happz added this to planning Jan 9, 2026
@happz happz added code | cli Changes related to the command line interface area | environment Environment variables handling ci | full test Pull request is ready for the full test execution labels Jan 9, 2026
@github-project-automation github-project-automation bot moved this to backlog in planning Jan 9, 2026
@happz happz moved this from backlog to review in planning Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area | environment Environment variables handling ci | full test Pull request is ready for the full test execution code | cli Changes related to the command line interface

Projects

Status: review

Development

Successfully merging this pull request may close these issues.

2 participants