docs: [CI-23943]: Document hyphenated output variable behavior with act 0.2.89 - #11871
Open
imaditya55 wants to merge 1 commit into
Open
imaditya55 wants to merge 1 commit into
imaditya55 wants to merge 1 commit into
Conversation
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.
…ct 0.2.89
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
Adds a note to the GitHub Action step docs (section: "Output variables from GitHub Actions steps") documenting a behavior change in the
github-actionsplugin images based on act v0.2.89 or later.With act v0.2.89, the env-file parser (godotenv) rejects variable names containing characters outside
[A-Za-z0-9_]and fails the entire step. The plugin now skips such names (e.g. hyphenated outputs likecache-hitandnode-versionfromactions/setup-node) when writing act's env file. These outputs remain available as Harness output variables and can be referenced normally in later steps/stages.This documents the change so support/customers have a reference if they notice hyphenated variables missing from the action's runtime environment after upgrading the plugin image.
Related plugin PR: drone-plugins/github-actions#32
Jira
https://harness.atlassian.net/browse/CI-24652
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: