Azure / Azure/azure-functions-powershell-worker
Add back E2E tests for 1ES official pipeline
- Dominant language
- C#
- Stars
- 215
- Forks
- 61
- Avg merge
- 21h 4m
- Merged PRs (30d)
- 6
Description
Due to increased security constriants, E2E tests were removed for the 1ES pipeline. We need to do the following to get them working again:
1. Figure out how to connect to KeyVault in 1ES private pipeline to run the Azure tests on public releases
2. Decide how much of the E2E logic we want running in the public pipeline, and refactor them to use Azure Storage Emulator/similar for purely local tests using Core Tools
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the existing 1ES private pipeline and the removed E2E test setup. Investigate KeyVault access for Azure tests on public releases, then determine which E2E logic can run publicly with Azure Storage Emulator or a similar Core Tools setup. Done means the agreed tests run under the appropriate pipeline constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- ci-cd, cloud, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100