microsoft / microsoft/AzureTRE
Add ability to reference core IP groups as destination in firewall rules
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 Azure TRE Developer
I want to define firewall rules in template_schema.json where I reference the TRE core's IP groups as destinations (and not only sources)
So that my firewall rules do not require brittle concatenation
Acceptance criteria
- Use of
destination_ip_groups_in_coreis supported, using the IP Groups' names, just likesource_ip_groups_in_core
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 in template_schema.json by tracing how source_ip_groups_in_core is represented and consumed. Extend the corresponding firewall-rule path for destination_ip_groups_in_core using core IP-group names, then verify templates accept destination references without brittle concatenation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud, networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100