Prisma Cloud Remediation - Invalid CLI script

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Prisma Cloud Remediation - Invalid CLI script

L0 Member

In Prisma Cloud SaaS, while creating custom remediation with cli commands, using custom variables or other cli command (such as grep) is not allowed apparently. Considering the following command, what could be the work-around to pass the output of the second gcloud command into the "rules" flag.


Following command successfully works on gcloud cli, however it produces "Invalid CLI script" error on Validation step;


gcloud compute --project=${account} firewall-rules update ${resourceName} --rules="$(gcloud compute --project=${account} firewall-rules list --filter="${resourceName}" | grep -o 'tcp:[^,]*' | grep -v 'tcp:22' | tr '\n' ',' | sed 's/,$//')"

  • 0 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!