Add StackSpot workflow job name

[franciscosenszup]

No description provided.

[gitbotzup]

PR Summary

This pull request introduces a new input parameter, stackspot-workflow-job, across multiple files in the repository. This parameter is required and is used to specify the name of the StackSpot Workflow Job. The changes ensure that this parameter is passed through the workflow configuration, action configuration, and entrypoint script, and is included in the API request payload for associating execution IDs.

Changed Files and Details

1. .github/workflows/bind.yml

   • Changes Summary:
     • Added a new input parameter stackspot-workflow-job to the workflow configuration.
     • This parameter is required and is used to specify the name of the StackSpot Workflow Job.
     • The parameter is passed to the job execution step.
   • Security Concerns:
     • Ensure that the stackspot-workflow-job input is validated and sanitized to prevent potential injection attacks or misuse.

2. action.yaml

   • Changes Summary:
     • Introduced a new input parameter stackspot-workflow-job in the action configuration.
     • This parameter is required and is passed to the entrypoint script.
     • The script now includes this parameter in its execution logic.
   • Security Concerns:
     • Verify that the stackspot-workflow-job input is properly validated to avoid potential security risks, such as command injection.

3. entrypoint.sh

   • Changes Summary:
     • Updated the script to handle the new stackspot-workflow-job parameter.
     • Added validation to check if the parameter is empty, and if so, the script exits with a status code of 0.
     • Modified the API request to include the stackspot-workflow-job in the payload for associating the GitHub execution ID with the workflow execution ID.
   • Security Concerns:
     • Ensure that the stackspot-workflow-job parameter is sanitized before being included in the API request payload to prevent injection vulnerabilities.
     • Verify that the API endpoint properly handles and validates the new parameter.

Security Advice

The addition of the stackspot-workflow-job parameter introduces potential security risks if not properly handled. Specifically:

• Input Validation and Sanitization: Ensure that the stackspot-workflow-job parameter is validated and sanitized at every stage (workflow, action, and script) to prevent injection attacks or misuse.
• API Endpoint Handling: Confirm that the API endpoint receiving the stackspot-workflow-job parameter has robust validation mechanisms to handle the new input securely.
• Command Injection Risks: Pay special attention to the entrypoint script to ensure that the parameter is not used in a way that could lead to command injection vulnerabilities.

Please review these changes carefully with the above security considerations in mind.

This is an AI-generated summary, which may be innacurate.
This aims only to assist human reviewers, and does not replace code reviews in any way.
Use responsibly and please submit any feedback to this form.