https://netsuiteprofessionals.com logo
Join Slack
Powered by
I'd be really interested in speaking to someone wh...
# sdf
s
I'd be really interested in speaking to someone who has successfully deployed Transaction Forms using Node CLI - it seems to me that validation for node cli is slightly different to that of ide plugins. IE i have an .xml form file which passes validation in one but fails in other with exact same values. Would be great to hear from someone who's using cli extensively for wide range of objects
a
When you run 
suitecloud project:deploy -i
Are you using local validate or server side validate?
I mean when it asks question about do you want to validate locally. Are you selecting YES? What happens if you say No?
still get the same errors?
s
🙂
validating locally results in those errors. validating in interactive mode against the account does not
since I had an authid configured against the right account I assumed running suitecloud project:validate would run it against the account
but running in interactive mode specifying the account works. thanks Ali!
and I just realised you could add the --server to accomplish the same in a CI workflow like 
suitecloud project:validate --server
a
Sorry i didn't suggest this before. But its a known issue in local validation. i assumed you are getting those errors from server side.
Keep in mind that when you deploy without interactive, it will validate locally by default. Only in interactive mode you can ignore local validate.
s
Got it thanks Ali
s
wait, does 
suitecloud project:validate --server
(i.e. no interactive mode) only validate server-side?
a
@stalbert Yes
s
ok thanks, from your previous comment I thought avoiding locale validate was only possible in interactive mode
a
That comment was for deploy. In non interactive mode deploy always go for local validate first. But validate can avoid local validate in both interactive and non interactive
s
hmmm. so non-interactive deploy will always do local validation - there is no way to avoid it?
a
I am afraid no. At least for now
s
bummer, with known local validation bugs that could be a blocker for folks trying to create automated deployment pipelines 😞
👍 1
s
@Ali Syed (NS DevTools QA) could you elaborate a little on the known issues for local validation?
@stalbert you could use something like Expect to automate the interactive input needed for 
suitecloud project:deploy -i
to bypass local validation. Let me know if you need a sample script.
s
Thanks @SimonC - I'm not actually fully automating (e.g. CI/CD) yet so don't mind waiting for 
suitecloud
to work out a couple of these kinks. That's a good idea for a workaround though
👍 1
Open in Slack
PreviousNext
Powered by