Troubleshooting tips for Lacework IaC in GitLab

[Kate_M]

Description	Need to troubleshoot GitLab pipeline configuration with Lacework IaC.
Scope	Lacework IaC in GitLab CI/CD
Solution	Common Troubleshooting Tips For either GitLab variations (SaaS/Self-Hosted): Ensure that the GitLab Prerequisites are in place Ensure that the required variables are in place (as saved variables for SaaS and passed environment variables for Self-Hosted): LW_ACCOUNT, LW_API_KEY, and LW_API_SECRET Ensure that the docker volume is getting mapped to the /app/src directory within the container (do not change this to a custom value): docker run --env-file env.list -v "$(pwd):/app/src" lacework/codesec-iac:latest When troubleshooting pipeline issues with the scanner, you can add troubleshooting commands to the script section of the pipeline yaml file in order to ascertain whether values are correct or being ingested from variables E.g., ls $SCAN_DIR Warning: Be careful not to expose secret values with the above approach   GitLab Self-Hosted Specifics Ensure that the correct runner config (docker executor) is in place Ensure network connectivity between GitLab runners and api.soluble.com  if encountering ‘failed to verify certificate’ errors, you may need to add the API endpoint’s root certificate to a proxy if runners are being proxied see the GoDaddy Certificate Chain - G2 section in https://certs.godaddy.com/repository for certificate information If the problem remains unresolved, please ​​​​​contact support.