microsoft / microsoft/AzureTRE
As part of end to end tests verify no connectivity to external resources from a VM within a workspace
Open
Nobody has claimed this yet.
story
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Description
As a TRE Developer
I want an E2E smoke test to verify there is no connectivity to external resources
So that I know that my code does not open up routes for data to be removed from a workspace
Acceptance criteria
Add an end to end test that:
- From a deployed VM inside the workspace tests there is no connectivity to Azure Storage external to the workspace
- From a deployed VM inside the workspace tests there is no connectivity to Docker Hub or Azure container registry external to the workspace
- From a deployed VM inside the workspace tests there is no connectivity to www.bing.com
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's end-to-end smoke-test entry point and the configuration used to deploy a VM inside a workspace. Run the existing E2E tests before adding coverage for Azure Storage, Docker Hub or Azure Container Registry, and www.bing.com; done means the deployed VM confirms each external resource is unreachable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, python
- Domain
- cloud, networking, security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100