This message was deleted.

See https://github.com/voxpupuli/puppet-nodejs#npm-packages It provides the nodejs installation and a package provider extention for npm. Regarding

npx

vs

npm

i can not help.

I think

npx

is kind of a convenience thing for running a node module's commands in the context of the local

package.json

, probably if you just use an

exec

resource and set the current directory to the directory of the

package.json

, you'll get the behavior you need. You may need to put the standard idempotency gates on that

exec

, though (i.e. figure out what file to look for with

creates

or what to check with

onlyif

or

unless

)

Thanks @Joel Wilson That was the path I'm currently going down.

are the variables

$::db_name

,

$::db_user

, etc top-scope variables? or where are they defined?

They are defined in another profile file that is being included in the role file. Sorry if that is not clear...but I'm still new to Puppet. @glee

if they are defined in another profile, you probably need to namespace them to reflect that ie:

${profile::other::dbname}

etc

OK, I'll try that

for reference: https://www.puppet.com/docs/puppet/7/lang_variables.html#lang_variables-variables-scope

this is my role file:

class role::strapi {
  include profile::nodejs::install
  include profile::postgresql::install
  include profile::postgresql::config_strapi_db
  include profile::nodejs::strapi_install
}

..and those variables are in the

profile::postgresql::config_strapi_db

ok, so

${profile::postgresql::config_strapi_db::db_name}

... etc

That still didn't work. I get this error:

Error: '/usr/bin/npx --yes create-strapi-app@latest my-proj                 --dbclient postgres --dbname                  --dbhost 127.0.0.1 --dbport 5432                 --dbusername  --dbpassword ' returned 1 instead of one of [0]
Error: /Stage[main]/Profile::nodejs::Strapi_install/Exec[npx create-strapi-app@latest my-proj]/returns: change from 'notrun' to ['0'] failed: '/usr/bin/npx --yes create-strapi-app@latest my-proj                 --dbclient postgres --dbname                  --dbhost 127.0.0.1 --dbport 5432                 --dbusername  --dbpassword ' returned 1 instead of one of [0] (corrective)

are those variables set or derived in the config profile? if they are derived it's possible that ordering means the config profile hasn't run yet so it hasn't set those values yet

the

db_name

,

db_user

are just a variable at top of file with a string value The

db_pass

is pulled in from and ENC eyaml file

if the config profile always must run first (before

profile::nodejs::strapi_install

, then you could possibly add a require to your strapi_install profile

OK, does that re-run config_strapi_db profile again?

but that could interfere with other dependencies etc depending on what other interactions you have with the other profiles

so the order they are listed in the role file doesn't do that?

no

so keep the long variable names

profile::.....::db_user

yes you need to keep the namespacing otherwise it won't know where those variables are from

OK, I'm closer. I did see that it was using the variables that were just defined as strings in the other profile working (

db_user

and

db_name

) however I'm getting this error now:

Error: sh: 1: S: not found

Error: /Stage[main]/Profile::nodejs::Strapi_install/Exec[npx create-strapi-app@latest my-proj]/returns: change from 'notrun' to ['0'] failed: sh: 1: S: not found
 (corrective)

so the script/command that the exec is running is returning not found?

I'm confused as this error doen't make any sense to me.. Maybe I force the

provider => shell

?

no

Well, this was running before...although the variables were wrong ( before I asked for help in here) , then I change the variables but they were referenced wrong. Now I have the require and correct path to variables...but getting this error that makes no sense to me 😕 Error: sh: 1: S: not found....

that error is saying the command that

exec

is running is returning "S: not found" -- ie: something called by npx (or the user profile that you're switching to) is passing

S

to the shell and causing it to return not found

I'm going to manually run that npx command as the strapi user to see what happens. I thought I did this before and it was fine...but I'll test again.

yeah i'd check that first. the other possibility is if the dbname/user/password has spaces or special chars they may need to be escaped for shell

Could special characters in the password be messing it up? I do see a

S

in the password...but there are some special characters too. So, I'm wondering if that is why it's messing up and returning the

S

?

do you need to quote the password when you pass it to shell manually?

yes

ok, so try adding quotes to your command for dbpassword -- replace the end of your command with:

--dbpassword \"${profile::postgresql::config_strapi_db::db_pass}\"",

I actually tried single quotes before you typed that......

so it will pass the quotes to the shell

currently running and I think might be working....

single quotes could work as well but i would probably escape them to be safe

yeh, the single quotes worked