This message was deleted.
# generals
sparse-intern-71089
03/16/2021, 1:29 PMThis message was deleted.
f
future-morning-96441
03/16/2021, 1:43 PMlooks like the postinstall script is failing. You could try to manually install the resource plugin by
pulumi plugin installs
shy-exabyte-78907
03/16/2021, 1:56 PMGot it @future-morning-96441. Where can I see the list of plugins I can install. In this case I need to install the
pulumi-nodejsf
future-morning-96441
03/16/2021, 2:05 PMI believe you can try just running
pulumi plugin installs
shy-exabyte-78907
03/16/2021, 2:14 PMUnfortunately, the same issue is still happening @future-morning-96441
f
future-morning-96441
03/16/2021, 2:15 PMdid
pulumi plugin installPULUMI_HOMEs
shy-exabyte-78907
03/16/2021, 2:17 PMPrints nothing, just finishes successfully and yes, the
PULUMI_HOMEshy-exabyte-78907
03/16/2021, 2:19 PMIt seems that the
PULUMI_HOMEf
future-morning-96441
03/16/2021, 2:19 PMis
pulumi plugin lss
shy-exabyte-78907
03/16/2021, 2:22 PMIt shows an empty list after the
pulumi plugin installf
future-morning-96441
03/16/2021, 3:50 PMhm, I'm not sure how you could proceed from here.
Did you find https://www.pulumi.com/docs/guides/continuous-delivery/azure-devops/ ?
future-morning-96441
03/16/2021, 3:53 PMWe used bitbucket pipelines and are currently moving to gitlab ci where we do the following steps iirc:
• use install script
• move the installed files to another dir, which can be accessed easier
• export PULUMI_HOME
• add pulumi dir to PATH
• .. other irrelevant stuff ..
• npm i
• pulumi plugin install
• someSetupScriptToCalculateMoreEnvironmentVars.sh
• pulumi update -s $PULUMI_STACK_NAME
10 Views