This message was deleted.

sparse-intern-71089

01/17/2020, 2:47 PM

This message was deleted.

powerful-football-81694

01/17/2020, 6:08 PM

@rhythmic-vegetable-87369 assuming you are using Azure Pipelines, you can map pipeline variables into environment variables using the

env

property on the step in your pipeline YAML.

powerful-football-81694

01/17/2020, 6:11 PM

I’m not sure exactly what you mean by “name or id of the pull request” and I don’t think there’s a pipeline variable that represents that. You can check the variable references here: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#build-variables

powerful-football-81694

01/17/2020, 6:13 PM

But you could for example use the

Build.SourceVersion

variable which represents the Git commit ID.

powerful-football-81694

01/17/2020, 6:16 PM

So you could do something like this in your YAML:

Copy code

- task: Pulumi@1
    inputs:
      ...
    env:
      COMMIT_ID: $(Build.SourceVersion)

And then in your Pulumi program, just read the environment variable

COMMIT_ID

and concatenate that to your resource names.

✔️ 1

tall-librarian-49374

01/17/2020, 9:26 PM

It may be helpful to describe your details in https://github.com/pulumi/pulumi/issues/1518

2 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.