Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run does not return stdout or stderr #198

Closed
Frassle opened this issue May 25, 2023 · 0 comments · Fixed by #267
Closed

run does not return stdout or stderr #198

Frassle opened this issue May 25, 2023 · 0 comments · Fixed by #267
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone

Comments

@Frassle
Copy link
Member

Frassle commented May 25, 2023

What happened?

See pulumi/pulumi#13013 (reply in thread) for initial user report on this.
I've tried repro'ing myself and can confirm that stdout and stderr are returned empty even for simple commands such as echo hi.

Expected Behavior

stdout and stderr to contain the output of the command ran.

Steps to reproduce

import * as command from "@pulumi/command";

// Render the Shell Script
const renderShell1 = command.local.run({
    command: "echo hello",
    environment: {
        //IMAGE_URL: imageurl,
        IMAGE_URL: "test123",
    },
  });
export const stdo = renderShell1.then(v => v.stdout);
export const stde = renderShell1.then(v => v.stderr);

Output of pulumi about

@pulumi/command 0.7.2

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@Frassle Frassle added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels May 25, 2023
@guineveresaenger guineveresaenger removed the needs-triage Needs attention from the triage team label May 30, 2023
@aq17 aq17 self-assigned this Aug 3, 2023
@mikhailshilkov mikhailshilkov added this to the 0.92 milestone Aug 7, 2023
@mikhailshilkov mikhailshilkov removed this from the 0.92 milestone Aug 11, 2023
@iwahbe iwahbe assigned iwahbe and unassigned aq17 Sep 12, 2023
iwahbe added a commit that referenced this issue Sep 12, 2023
By moving `run` from a method on `*CommandOutputs` to it's own function, we make it obvious
what it effects. This has the advantage of making it operate seamlessly on both
`CommandOutputs` and `RunOutputs`.

Fixes #198
@iwahbe iwahbe mentioned this issue Sep 12, 2023
iwahbe added a commit that referenced this issue Sep 13, 2023
By moving `run` from a method on `*CommandOutputs` to it's own function, we make it obvious
what it effects. This has the advantage of making it operate seamlessly on both
`CommandOutputs` and `RunOutputs`.

Fixes #198
iwahbe added a commit that referenced this issue Sep 13, 2023
By moving `run` from a method on `*CommandOutputs` to it's own function,
we make it obvious what it effects. This has the advantage of making it
operate seamlessly on both `CommandOutputs` and `RunOutputs`.

Fixes #198
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Sep 13, 2023
@mikhailshilkov mikhailshilkov added this to the 0.94 milestone Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants