How can change ExecutionPolicy in Powershell,how can solve this error - powershell-2.0

scrrenshot
I want to change the execution policy for create virtual env in python ,screenshot of the error, how can solve it

Related

Having issues with all ASK CLI commands not working

Every ASK CLI command that I try to run, whether in CMD or Powershell, aborts and provides me with this error:
[Error]: TypeError: Cannot convert undefined or null to object
I have tried many versions of Node and ASK CLI to no avail. I'm not sure if I'm being foolish as there's no other instances of anyone having this issue with ASK CLI but any help would be appreciated, thanks.
Image of Error Message

Running terragrunt run-all destroy in Jenkins needs user input

I am currently using terragrunt to manage my terraform code, and am running into an error when trying to destroy my infrastructure. I want to be able to spin up development environments (or parts of environments) and delete them easily through Jenkins.
A certain part of my infrastructure is structured so that I need to use the terragrunt run-all command, which results in the following user message: WARNING: Are you sure you want to run `terragrunt destroy` in each folder of the stack described above? There is no undo! (y/n). Jenkins immediately fails after this output as it expects a y/n input.
For apply I have managed to go around this by saving a plan and then applying it, however for the destroy command I can't find another way. terraform commands have an -auto-approve option, but this seems to do nothing to the terragrunt run-all command, despite this being in the documentation:
Using run-all with apply or destroy silently adds the -auto-approve flag to the command line arguments passed to Terraform due to issues with shared stdin making individual approvals impossible.
Does anyone have any experience of this or any advice? Am I misunderstanding the documentation?
Just in case anyone else is looking for an answer to this, the flag --terragrunt-non-interactive can be used.

Apparmor aa-genprof /etc/apparmor.d//local/usr.lib.dovecot.anvil not found

Hi I`m new to using apparmor. So i created a simple script on my Debian 10 to look how apparmor works:
#! /bin/sh
echo "hi from Apparmor">/tmp/hi.txt
cat /tmp/hi.txt
rm /tmp/hi.txt
Then I saved the file as s.sh and try to generate a profile:
Please tell me how i can solve this problem.
Thank for any answer!
This is a known bug in Debian Buster.
You can solve this by creating missing files until it works.
Source :
In the following example, we will thus try to create a profile for /sbin/dhclient. For this we will use aa-genprof dhclient. In Debian Buster there is a known bug[6] that makes the previous command fail with the following error: ERROR: Include file /etc/apparmor.d/local/usr.lib.dovecot.deliver not found. To fix it create the missing files with touch file. It will invite you to use the application in another window and when done to come back to aa-genprof to scan for AppArmor events in the system logs and convert those logs into access rules. For each logged event, it will make one or more rule suggestions that you can either approve or further edit in multiple ways:
https://debian-handbook.info/browse/fr-FR/stable/sect.apparmor.html

Problem with Jenkins running Robot Framework script

I am trying to automate the execution of Robot Framework using Jenkins.
But when I run Jenkins I am receiving the error "Permission denied". You can see bellow the error's print screen.
Despite several attenpts Im not able to identify where this restriction is.
I have already include the Jenkins user as SUDO user, but the error is still there.
I also applied o CHMOD 777 /home/eduardo/.local/bin/robot but did not solve.
Can someone please tell me how I can identify where this restriction (Permission denied) is.
Thank in advance.

Change go path explicitly on docker image

when I run dep ensure
/home/jenkins/workspace/myproject-voter is not within a known GOPATH/src
we have go installed on this docker image , I know that the project is not cloned to go/src but my question is if via set env or something I can do some trick to overcome this issue ?
my question is if via set env or something I can do some trick to overcome this issue ?
Not "set env", but ENV:
ENV GOPATH=/path/to/your/Go/project
That would ensure any Go command is using the right workspace.

Resources