1

I have a Windows Elastic Beanstalk instance. I have the following commands.config in my project's .ebextensions

commands:
  00-install-choco:
    command: |
        powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))"
  01-set-choco-path:
    command: |
        SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin

These two commands are working. However, I also have a container-commands.config file which needs to call upon choco, but it keeps failing due to 'choco' is not recognized as an internal or external command

container_commands:
  01-install nssm:
    command: |
        choco install nssm -y

How do I get subsequent commands to pick up the updated PATH? Is there a more appropriate approach to installing binaries and setting them to Window's PATH during ESB instance creation?

I attempted to follow https://aws.amazon.com/blogs/developer/using-nuget-and-chocolatey-package-managers-in-aws-cloudformation-and-aws-elastic-beanstalk/

files:
  c:/tools/ewmp.cmd:
    content: |
      @ECHO OFF
      FOR /F "tokens=3,*" %%a IN ('REG QUERY "HKLMSystemCurrentControlSetControlSession ManagerEnvironment" /v PATH') DO PATH %%a%%b
      %*
commands:
  01-install-choco:
    command: powershell -NoProfile -ExecutionPolicy unrestricted -Command "Invoke-Expression ((New-Object Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"
    waitAfterCompletion: 0
  02-install-nssm:
    command: c:/tools/ewmp choco install nssm -y
    waitAfterCompletion: 0

But even that gives me similar errors.

-----------------------Command Output-----------------------
ERROR: Invalid key name.
Type "REG QUERY /?" for usage.
'choco' is not recognized as an internal or external command,
operable program or batch file.
------------------------------------------------------------
Display name
  • 1,109
  • 1
  • 15
  • 31

1 Answers1

1

I am not a user of Elastic Beanstalk, so I can't speak to whether this will work or not, but according to the documentation it is necessary to provide an additional command to update to PATH variable that is used:

The Chocolatey installer and the packages it installs may modify the machine’s PATH environment variable. This adds complexity since subsequent commands after these installations are executed in the same session, which does not have the updated PATH. To overcome this, we utilize a command file to set the session’s PATH to that of the machine before it executes our command.

files:
  c:/tools/ewmp.cmd:
    content: |
      @ECHO OFF
      FOR /F "tokens=3,*" %%a IN ('REG QUERY "HKLMSystemCurrentControlSetControlSession ManagerEnvironment" /v PATH') DO PATH %%a%%b
      %*
commands:
  00-install-choco:
    command: powershell -NoProfile -ExecutionPolicy unrestricted -Command "Invoke-Expression ((New-Object Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"
container_commands:
  01-install nssm:
    command: |
      c:toolsewmp choco install nssm -y

NOTE: The one thing I am not clear on, based on the documentation, is the usage of c:toolsewmp rather than c:/tools/ewmp in the command section. I don't know if this is an escaping issue in the code that is being rendered to the browser in the documentation, or whether this is intentional. You may need to play with this to see what works.

Gary Ewan Park
  • 17,610
  • 5
  • 42
  • 60
  • Even with playing with different usages of ewmp, this still gives me a not recognized error. `ERROR: Invalid key name. 'choco' is not recognized as an internal or external command` – Display name Mar 27 '19 at 15:02
  • But that AWS blog post is a good find! It does explain why the PATH isn't being picked up. – Display name Mar 27 '19 at 15:36
  • Did you try the example from the article? Could it be something to do with the container command? – Gary Ewan Park Mar 27 '19 at 19:32