https://pulumi.com
Join Slack
This message was deleted.
# automation-api
s
This message was deleted.
l
Looks like an error message, probably beginning with "y", is being returned at some point when a valid response (maybe json-like) is expected. No way to tell where the error is from this.
You may need to start bisecting...
t
yeah I went down that route yesterday and like I said, just moving my code resolved the issue. I am fairly certain i didn't change anything to cause an error
narrowed it down, it ONLY happens when I try to selectStack:
Copy code
const appSvcsStack = LocalWorkspace.selectStack({
    stackName: `RedJade/qa/app-services`,
    workDir: ".",
  });
  const appSvcsOuts = await (await appSvcsStack).outputs();
which is definitely code that I have seen work repeatedly (found this function in the code -- not 100% sure I'm using it right)
b
@tall-scientist-89115 the error appears to come from the golang JSON encoder: https://go.googlesource.com/go/+/master/src/encoding/json/decode_test.go#460 what's in your stack outputs?
t
interestingly enough, changing the working directory to any directory other than the two directories which have encountered the problem before and it goes away edit: got a 409 "another update in progress" in that case
This comes from the same program but with a different working directory
just_the_app-svcs_stack_but_it_validates.txt
I suppose a different question is: What's the best way to select an arbitrary stack outputs programmatically without messing with a workDir? I'm happy to help figure this out though I'm curious at this point
Super works, but probably not for very long
Copy code
const appSvcsStack = LocalWorkspace.selectStack({
    stackName: `RedJade/qa/app-services`,
    workDir: "../..",
  });
edit: this does escape all Pulumi projects though, so maybe it doesn't break..I'll let you guys know.
r
Hey what versions of pulumi SDK and CLI are you using?
This is definitely odd.
t
cli is v3.1.0
sdk is also 3.1
r
A couple of things. I’m curious what your automation api script is doing. Are there many stacks? Are you selecting them concurrently? I think you mentioned that you only want to get the stack outputs, is that right? The next release will expose a 
LocalWorkspace.stackOutputs(stackName: string)
method which will enable you to get the stack outputs without selecting each stack. I still would like to get down to the bottom of whats going on here though.
t
I am selecting them concurrently but once the problem begins it will also happen for just 1. That method looks perfect!
I can vscode live share or just copy paste/describe it here
which do you prefer?
r
I am selecting them concurrently
I think that might be the issue. 
selectStack
modifies global state and might be causing some unexpected behavior.
t
for sure that makes sense to me
r
copy/paste describing would be great! I’m about to head off to bed so being able to take a closer look later would be really helpful
t
So here's the folder structure, the scripts folder having its own dependency chain separate from the infra folder's is largely unnecessary and was done in response to the problem yesterday
r
Yeah just from a quick glance I’m guessing things are going wrong here:
Copy code
return await Promise.all([appSvcsStack, clusterStack, containerStack]).then(
    ([appSvcsStack, clusterStack, containerStack]) => {
      elapsed_time("fetching stacks");
      return Promise.all([appSvcsStack.outputs(), clusterStack.outputs(), containerStack.outputs()]).then(
        ([appSvcsOuts, clusterOuts, containerOuts]) => {
I think if you did the 
selectStack
step serially:
Copy code
const appSvcsStack = await LocalWorkspace.selectStack({
    stackName: `RedJade/qa/app-services`,
    workDir: "..",
});
const clusterStack = await LocalWorkspace.selectStack({
    stackName: `RedJade/${projectName}/cluster-configuration`,
    workDir: "..",
});
const containerStack = await LocalWorkspace.selectStack({
    stackName: `RedJade/global/container-registry`,
    workDir: "..",
});

return Promise.all([appSvcsStack.outputs(), clusterStack.outputs(), containerStack.outputs()]).then(
    ([appSvcsOuts, clusterOuts, containerOuts]) => {
        elapsed_time("fetching stack outputs");
        return { ... }
and then the rest of your workflow I think you would be okay.
t
haha yeah, the problem is the die is cast
leme rename the script folder and try tha
r
haha yeah, the problem is the die is cast
Ah interesting, once it gets borked theres no recovering it huh?
t
yeah isolating down to one and doing as you said it is done
new terminal, restarting the computer
r
t
nice find
yeah i saw that before opening this thread but his was "r" instead of "y", but I eventually saw that one too whenever the "../.." (which is outside my pulumi infra folder) borked out
renaming the folder did nothing, going to try reinstalling the CLI
r
In any case, I think we need to take a look at the 
selectStack
functionality, especially for folks who might want to be doing tasks like getting outputs or destroying multiple stacks who don’t need the global state modifying behavior of 
selectStack
.
👍 1
renaming the folder did nothing, going to try reinstalling the CLI
honestly not sure if that’s going to help. can you go to that dir (the one workdir points to) and just try using the pulumi CLI to run 
pulumi stack ls
?
t
seems good
Copy code
pulumi stack ls
NAME                           LAST UPDATE     RESOURCE COUNT  URL
RedJade/app-services           7 hours ago     67              <https://app.pulumi.com/RedJade/qa/app-services>
RedJade/cluster-configuration  1 week ago      29              <https://app.pulumi.com/RedJade/qa/cluster-configuration>
RedJade/cluster-services       6 days ago      58              <https://app.pulumi.com/RedJade/qa/cluster-services>
RedJade/identity               1 week ago      16              <https://app.pulumi.com/RedJade/qa/identity>
RedJade/managed-infra          1 week ago      7               <https://app.pulumi.com/RedJade/qa/managed-infra>
RedJade/staging-apps           1 day ago       0               <https://app.pulumi.com/RedJade/qa/staging-apps>
RedJade/staging-database       52 minutes ago  0               <https://app.pulumi.com/RedJade/qa/staging-database>
staging-database               5 hours ago     0               <https://app.pulumi.com/mypersonalaccount/qa/staging-database>
is the global state being modified on your servers then? I've at various points tried deleting the stack and that didn't seem to have any effect, going to try that again right now just to make sure my memory isn't lying
or maybe I shouldn't muck with it
feel free to deal with this in the morning, we can arrange a call if it helps
I won't go mucking with state so maybe you can get a repro on it
r
Okay yeah let’s check in tomorrow 🙏🏽
Will be easier to debug on a call, thanks for bearing with us @tall-scientist-89115!
t
hey np, thanks for the great product/all your help up to this point
unlike 
pulumi stack ls
, JUST 
pulumi stack
does produce the error (as does 
pulumi up
)
Copy code
pulumi stack      
error: invalid character 'y' after top-level value
 ✘(qa-aks4a68d4e2)
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by