Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A common problem we have been running into with importing customer channels is they often use environmental variables which off the bat we do not have in our environmentsset up on our Iguana instances.

To deal with this one little workaround tool we have in the importer in the shim library is to override os.getenv with a little wrapper which give default values for undefined environmental variables and it stored them all in a global table which you view.

The shim populates an environmental variable _EnvVarList. This means you can inspect it with a trace statement so that you can see all the env variables which a component is using:Image Removed

...

This is the source code:

...