-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an $IsAzureFunctions #81
Comments
While there's other ways to check for this in general, I agree it's low
impact and low effort, no valid reason not to have it other than backlog
(and unlikely but possible variable conflicts for those new to the
platform)
…On Thu, Oct 25, 2018, 11:05 AM Tyler James Leonhardt < ***@***.***> wrote:
Similar to $IsWindows, $IsMacOS, $IsLinux
Just a helper global variable that says whether a script is running in
Azure Functions
cc/ @joeyaiello <https://github.com/joeyaiello> @SteveL-MSFT
<https://github.com/SteveL-MSFT>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#81>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOjVUho2_9kHcUShUAlRw0PQhdLrRhk7ks5uof1cgaJpZM4X6z9l>
.
|
Alternatively, if Azure Functions already exposes an Environment variable, we could possibly leave it at that. @asavaritayal @pragnagopa and idea if this is a thing? |
Was thinking about how to get that the other day. I want to test my PS code locally but emit the results to |
Good point @dfinke something like this could enable users to write scripts that would work locally and in Azure Functions. |
Let's talk to the AzF team about adding an environment variable to the host that tells you you're in an Azure Function. |
Today they rely on:
It would probably be nice to have a more customer friendly env var. |
There are a number of this including WEBSITE_INSTANCE_ID. |
Similar to
$IsWindows
,$IsMacOS
,$IsLinux
Just a helper global variable that says whether a script is running in Azure Functions
cc/ @joeyaiello @SteveL-MSFT
The text was updated successfully, but these errors were encountered: