Automate PowerShell Response to prompt












1















Creating a PowerShell script that calls an apps cmdlet. When then cmdlet runs it prompts for a response and the scripts hangs. The cmdlet doesn't have any parameters for this. Is there any way to respond programmatically? I tried ECHO but that doesn't work.
script hanging










share|improve this question


















  • 1





    Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

    – Drew
    Nov 16 '18 at 2:37
















1















Creating a PowerShell script that calls an apps cmdlet. When then cmdlet runs it prompts for a response and the scripts hangs. The cmdlet doesn't have any parameters for this. Is there any way to respond programmatically? I tried ECHO but that doesn't work.
script hanging










share|improve this question


















  • 1





    Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

    – Drew
    Nov 16 '18 at 2:37














1












1








1


1






Creating a PowerShell script that calls an apps cmdlet. When then cmdlet runs it prompts for a response and the scripts hangs. The cmdlet doesn't have any parameters for this. Is there any way to respond programmatically? I tried ECHO but that doesn't work.
script hanging










share|improve this question














Creating a PowerShell script that calls an apps cmdlet. When then cmdlet runs it prompts for a response and the scripts hangs. The cmdlet doesn't have any parameters for this. Is there any way to respond programmatically? I tried ECHO but that doesn't work.
script hanging







powershell






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 2:36









TMAC 23TMAC 23

133




133








  • 1





    Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

    – Drew
    Nov 16 '18 at 2:37














  • 1





    Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

    – Drew
    Nov 16 '18 at 2:37








1




1





Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

– Drew
Nov 16 '18 at 2:37





Without seeing the *assessment.ps1 script, unable to check if you can pass params to it.

– Drew
Nov 16 '18 at 2:37












1 Answer
1






active

oldest

votes


















3














The only way to get PowerShell scripts that solicit input via the host - typically, via Read-Host - to read input from the pipeline instead of from the keyboard is to use to run the script as an external PowerShell instance.



A simple example:



# Does NOT work: pipeline input is IGNORED and Read-Host "hangs", i.e.,
# it waits for interactive input.
'y' | & { Read-Host "Y/N?" }


# OK: By launching the command via a new PowerShell instance,
# Read-Host reads from the pipeline (stdin).
# To run a script file externally, use -file instead of -command.
'y' | powershell -noprofile -command 'Read-Host "Y/N?"'


Note: Running the script / command via an external PowerShell instance comes at a cost:




  • Creating a new PowerShell process is costly in terms of performance.



  • Output from the new instance will be textual (strings) by default, not objects.




    • You can approximate the usual in-process experience by passing -OutputFormat xml to the external instance and post-processing the results via Import-CliXml, but that has limitations.








share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53330644%2fautomate-powershell-response-to-prompt%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    The only way to get PowerShell scripts that solicit input via the host - typically, via Read-Host - to read input from the pipeline instead of from the keyboard is to use to run the script as an external PowerShell instance.



    A simple example:



    # Does NOT work: pipeline input is IGNORED and Read-Host "hangs", i.e.,
    # it waits for interactive input.
    'y' | & { Read-Host "Y/N?" }


    # OK: By launching the command via a new PowerShell instance,
    # Read-Host reads from the pipeline (stdin).
    # To run a script file externally, use -file instead of -command.
    'y' | powershell -noprofile -command 'Read-Host "Y/N?"'


    Note: Running the script / command via an external PowerShell instance comes at a cost:




    • Creating a new PowerShell process is costly in terms of performance.



    • Output from the new instance will be textual (strings) by default, not objects.




      • You can approximate the usual in-process experience by passing -OutputFormat xml to the external instance and post-processing the results via Import-CliXml, but that has limitations.








    share|improve this answer






























      3














      The only way to get PowerShell scripts that solicit input via the host - typically, via Read-Host - to read input from the pipeline instead of from the keyboard is to use to run the script as an external PowerShell instance.



      A simple example:



      # Does NOT work: pipeline input is IGNORED and Read-Host "hangs", i.e.,
      # it waits for interactive input.
      'y' | & { Read-Host "Y/N?" }


      # OK: By launching the command via a new PowerShell instance,
      # Read-Host reads from the pipeline (stdin).
      # To run a script file externally, use -file instead of -command.
      'y' | powershell -noprofile -command 'Read-Host "Y/N?"'


      Note: Running the script / command via an external PowerShell instance comes at a cost:




      • Creating a new PowerShell process is costly in terms of performance.



      • Output from the new instance will be textual (strings) by default, not objects.




        • You can approximate the usual in-process experience by passing -OutputFormat xml to the external instance and post-processing the results via Import-CliXml, but that has limitations.








      share|improve this answer




























        3












        3








        3







        The only way to get PowerShell scripts that solicit input via the host - typically, via Read-Host - to read input from the pipeline instead of from the keyboard is to use to run the script as an external PowerShell instance.



        A simple example:



        # Does NOT work: pipeline input is IGNORED and Read-Host "hangs", i.e.,
        # it waits for interactive input.
        'y' | & { Read-Host "Y/N?" }


        # OK: By launching the command via a new PowerShell instance,
        # Read-Host reads from the pipeline (stdin).
        # To run a script file externally, use -file instead of -command.
        'y' | powershell -noprofile -command 'Read-Host "Y/N?"'


        Note: Running the script / command via an external PowerShell instance comes at a cost:




        • Creating a new PowerShell process is costly in terms of performance.



        • Output from the new instance will be textual (strings) by default, not objects.




          • You can approximate the usual in-process experience by passing -OutputFormat xml to the external instance and post-processing the results via Import-CliXml, but that has limitations.








        share|improve this answer















        The only way to get PowerShell scripts that solicit input via the host - typically, via Read-Host - to read input from the pipeline instead of from the keyboard is to use to run the script as an external PowerShell instance.



        A simple example:



        # Does NOT work: pipeline input is IGNORED and Read-Host "hangs", i.e.,
        # it waits for interactive input.
        'y' | & { Read-Host "Y/N?" }


        # OK: By launching the command via a new PowerShell instance,
        # Read-Host reads from the pipeline (stdin).
        # To run a script file externally, use -file instead of -command.
        'y' | powershell -noprofile -command 'Read-Host "Y/N?"'


        Note: Running the script / command via an external PowerShell instance comes at a cost:




        • Creating a new PowerShell process is costly in terms of performance.



        • Output from the new instance will be textual (strings) by default, not objects.




          • You can approximate the usual in-process experience by passing -OutputFormat xml to the external instance and post-processing the results via Import-CliXml, but that has limitations.









        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 16 '18 at 3:09

























        answered Nov 16 '18 at 3:02









        mklement0mklement0

        137k22255292




        137k22255292
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53330644%2fautomate-powershell-response-to-prompt%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The Sandy Post

            Danny Elfman

            Pages that link to "Head v. Amoskeag Manufacturing Co."