add azure pipeline examples

[cjanslow]

Affected Components

• Content & Marketing
• Pricing
• Test
• Docs
• Learn
• Other

Pre-Requisites

• Code is linted (npm run lint)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
checklyhq-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 6, 2024 1:44pm

[checklyalex]

should the azure-pipelines.yml contain a environment var to be passed to the staging env? Do we need to pass anything to the feature branch to make Checkly aware of the env its running on or have I missed something?

Could we also prepare a short code snippet which shows the fetched vault secrets being used with npx checkly env add or update before running the tests?

[cjanslow]

@checklyalex

should the azure-pipelines.yml contain a environment var to be passed to the staging env?

I'm not sure what you mean by this. Can you please clarify?

Do we need to pass anything to the feature branch to make Checkly aware of the env its running on or have I missed something?

Do you mean for how it detects whether it runs E2EStaging or E2EProduction? This is detected by the condition set for each. For example, E2EStaging has this condition:

        condition: and(succeeded(), ne(variables['Build.SourceBranch'], 'refs/heads/main'))

This checks that the head of the SourceBranch is ne() --> not equal to main. For E2EProduction, it is the opposite using eq() --> equal. Let me know if that is not what you were asking.

Could we also prepare a short code snippet which shows the fetched vault secrets being used with npx checkly env add or update before running the tests?

I'm not sure I understand the use case of this. How do customers generally use key vault to pass secrets to Checkly, and are they generally happy to sync them in to Checkly as env vars? This almost feels like they'd want to fetch the secrets at run-time, rather than store them in Checkly.