PR Pipeline: Fix Env Deployment Error

[mikaelweave]

Description

Currently, if you have a PR running and you push changes while the environment is deploying you can get transient errors because the existing PR pipeline is canceled and a new one is queued. The deployment will not succeed because an existing deployment with the same name is running.

I considered:

• Making the name unique
• Seeing if an existing deployment is there

In the end I checked for an existing deployment - should make the pipeline execute faster and less error prone to conflicts.

Error I was seeing

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)