If I need to, I can pass it through bash. I just don't know how (with the ability to get the values back).

You have sparked a fascinating discussion, making me wonder whether "only bash can parse a bash script"...

Meanwhile, you could get bash to do the work for you, I think, if you try the following steps:

• Make sure "#!/bin/bash" is at the top of your bash script file (or whatever the appropriate path is for bash on your system).
• Make sure that the script (or your current shell environment) has PATH set to include the "env" command (this is /usr/bin/env on my BSD-like macosx system), and append a line at the end of the script that is just "env" (i.e. to have the script run that command after it has done everything else).
• Make the script file executable (chmod +x ...)
• Run a perl one-liner like the following.

perl -e '$env = `your_bash_script.file`; print $env,$/'
[download]

Maybe you want to redirect the output of that to a file. Note that the output will include everything in your current shell environment, along with everything declared by the bash script. If you also run a one-liner like this:

perl -e '$env = `bash -c env`; print $env,$/'
[download]

and compare that output to the one involving your bash script, you'll be able to "subtract out" the "ambient environment", and isolate the stuff that comes from the script.

There might be other ways to do the same thing, but this was the first one I found (and I'll confess it took several iterations to figure it out).

UPDATE: Just putting "env" at the end entails a simplistic assumption that the bash script will execute more or less linearly from top to bottom. But if there are multiple points in the script where processing could end under different conditions (and especially if more than one of these exit points qualifies as "success"), you would need to add the "env" command at every such point. Good luck with that...