Marco Ruta
08/08/2024, 6:57 PMMarvin
08/08/2024, 6:57 PMrun_shell_script
utility is correctly configured to set up the repository environment before cloning.
Example:
yaml
pull:
- prefect.deployments.steps.run_shell_script:
id: set-env
script: export GIT_SSL_NO_VERIFY=true
expand_env_vars: true
- prefect.deployments.steps.git_clone:
repository: "<https://gitlab.com/your/repo.git>"
access_token: "{{ prefect.blocks.secret.gitlab-token }}"
4. Support for HTTP:
Ensure that HTTP is supported for the repository URL in the way you are using Prefect blocks. Occasionally issues can arise if only certain protocols are supported or configured.
GitHub issue discussing HTTP support: GitHub Issue
5. Logs and Debugging:
Check the logs for more detailed error messages that might give insights into why the exit code 128
is occurring.
If after checking these suggested steps the problem persists, you may want to raise a more detailed issue (if not already) on the Prefect GitHub repository for more targeted support.
Feel free to ask further questions if needed.