So I'm very new to vRO (less than 48 hours), but I'm getting the hang of it.
I'm porting a powershell script over to vRO for reasons that I don't want to get into (long political story). I'm having a problem specifying custom headers to the "Invoke a REST operation" workflow within my custom workflow. The specific headers should look like this:
"x-isi-ifs-target-type" = "container"
"x-isi-ifs-access-control" = 770
(the target-type container is mandatory, the other one isn't)
When I look at the Invoke a REST operation workflow, I see that it has some inputs called headerParamX (where X = [0..9]). I've figured that was going to be my key to victory, however no victory has been obtained.
I've created an attribute named fheader1, set the type to string, and put the value at "x-isi-ifs-target-type" = "container". I then bound fheader1 to headerParam0. However when I run the workflow, here is the relevant output:
[2019-04-24 08:02:04.335] [I] ****Headers****
[2019-04-24 08:02:04.337] [I] container
[2019-04-24 08:02:04.338] [I] Wed, 24 Apr 2019 13:50:17 GMT
[2019-04-24 08:02:04.340] [I] 1.0
[2019-04-24 08:02:04.341] [I] timeout=15, max=500
[2019-04-24 08:02:04.342] [I] Apache/2.4.29 (FreeBSD) OpenSSL/1.0.2o-fips mod_fastcgi/mod_fastcgi-SNAP-0910052141
[2019-04-24 08:02:04.344] [I] Wed, 24 Apr 2019 15:02:04 GMT
[2019-04-24 08:02:04.345] [I] GET, PUT, POST, DELETE, HEAD
[2019-04-24 08:02:04.347] [I] application/json
[2019-04-24 08:02:04.348] [I] 0777
[2019-04-24 08:02:04.349] [I] chunked
[2019-04-24 08:02:04.351] [I] Keep-Alive
[2019-04-24 08:02:04.352] [I] "4294967298-18446744073709551615-266"
[2019-04-24 08:02:04.388] [I] Setting defaut content type to:
[2019-04-24 08:02:04.389] [I] acceptHeaders null
[2019-04-24 08:02:04.404] [I] Content as string:
{"errors" : [
{
"code" : "AEC_ARG_REQUIRED",
"message" : "'x-isi-ifs-target-type' must be set."
}
]
}
It looks like it sent the parameter container but may not have given it the right name? I'm not sure. I've tried a few different formatting options as well, removing quotes, etc. I've also seen that most people tend to just write their own REST calls in javascript and use "Scriptable task", but that sort of defeats my purpose of trying to put this into a format that "non-scripters" can read (again, long political story).
Please random people from the internet, tell me what I'm doing wrong. My poor hairline can't take it anymore...