Environment Variables expansion

[nuxlli]

Due to a logic issue, the command property of the web system in the excerpt below didn't work. In the other hand, the command of the worker system was working normally.

systems({
  web: {
    image: { docker: "azukiapp/ruby" },
    command: ["bundle", "exec", "rails", "-p", "$HTTP_PORT"],
  },
  worker: {
    image: { docker: "azukiapp/ruby" },
    command: "bundle exec rails -p $HTTP_PORT",
  },
});

The reason for it is that, in the case of the system worker, the command was sent to Docker as /bin/sh -c "[command]" and, therefore, the HTTP_PORT var was properly expanded.

In the case of the web system, the bundle command was executed directly, without variables expansion by a subshell (/bin/sh).

To solve this issue, two major changes was done:

• The support for variables expansion using ${} and, less used but still available, <%%> in the Azkfile, have been deprecated;
• Variables defined as ${UPPER_CASE_VAR_NAME} or $UPPER_CASE_VAR_NAME are expanded automatically;

Finally, the docs has a new session with a detailed explanation of how env vars are processed.

[saitodisse]

This looks very nice.