Skip to content

Conversation

omus
Copy link
Member

@omus omus commented Feb 26, 2025

Functionality to disable the creation of these environmental variables was added in 5.7.0

Copy link

sh-checker report

To get the full details, please check in the job output.

shellcheck errors

'shellcheck ' returned error 1 finding the following syntactical issues:

----------

In workflow_scripts/integration-tests.yaml/job=Test_{{_matrix.test.title_}}/step=Validate_docker-metadata-output_environment_variables_are_overwritten.sh line 4:
if [[ "$(printenv | grep -c '^DOCKER_METADATA_OUTPUT_' -gt 0 ]]; then
      ^-- SC1009 (info): The mentioned syntax error was in this double quoted string.
       ^-- SC1073 (error): Couldn't parse this command expansion. Fix to allow more checks.
                                                                     ^-- SC1072 (error): Unexpected keyword/token. Fix any mentioned problems and try again.

For more information:
  https://www.shellcheck.net/wiki/SC1072 -- Unexpected keyword/token. Fix any...
  https://www.shellcheck.net/wiki/SC1073 -- Couldn't parse this command expan...
  https://www.shellcheck.net/wiki/SC1009 -- The mentioned syntax error was in...
----------

You can address the above issues in one of three ways:
1. Manually correct the issue in the offending shell script;
2. Disable specific issues by adding the comment:
  # shellcheck disable=NNNN
above the line that contains the issue, where NNNN is the error code;
3. Add '-e NNNN' to the SHELLCHECK_OPTS setting in your .yml action file.



shfmt errors

'shfmt ' returned error 1 finding the following formatting issues:

----------
workflow_scripts/integration-tests.yaml/job=Test_{{_matrix.test.title_}}/step=Validate_docker-metadata-output_environment_variables_are_overwritten.sh:4:66: "then" can only be used in an if
----------

You can reformat the above files to meet shfmt's requirements by typing:

  shfmt  -w filename


Copy link

sh-checker report

To get the full details, please check in the job output.

shellcheck errors

'shellcheck ' returned error 1 finding the following syntactical issues:

----------

In workflow_scripts/integration-tests.yaml/job=Test_{{_matrix.test.title_}}/step=Validate_docker-metadata-output_environment_variables_are_overwritten.sh line 4:
if [[ "$(printenv | grep -c '^DOCKER_METADATA_OUTPUT_' -gt 0 ]]; then
      ^-- SC1009 (info): The mentioned syntax error was in this double quoted string.
       ^-- SC1073 (error): Couldn't parse this command expansion. Fix to allow more checks.
                                                                     ^-- SC1072 (error): Unexpected keyword/token. Fix any mentioned problems and try again.

For more information:
  https://www.shellcheck.net/wiki/SC1072 -- Unexpected keyword/token. Fix any...
  https://www.shellcheck.net/wiki/SC1073 -- Couldn't parse this command expan...
  https://www.shellcheck.net/wiki/SC1009 -- The mentioned syntax error was in...
----------

You can address the above issues in one of three ways:
1. Manually correct the issue in the offending shell script;
2. Disable specific issues by adding the comment:
  # shellcheck disable=NNNN
above the line that contains the issue, where NNNN is the error code;
3. Add '-e NNNN' to the SHELLCHECK_OPTS setting in your .yml action file.



shfmt errors

'shfmt ' returned error 1 finding the following formatting issues:

----------
workflow_scripts/integration-tests.yaml/job=Test_{{_matrix.test.title_}}/step=Validate_docker-metadata-output_environment_variables_are_overwritten.sh:4:66: "then" can only be used in an if
----------

You can reformat the above files to meet shfmt's requirements by typing:

  shfmt  -w filename


@omus omus requested a review from MKVatinyan February 27, 2025 14:52
@omus omus merged commit be676eb into main Feb 27, 2025
10 checks passed
@omus omus deleted the cv/disable-metadata-env branch February 27, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants