Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated update of shared service properties - rule on the firewall, package on package mirror #23

Closed
8 tasks done
christoferlof opened this issue Mar 12, 2021 · 1 comment
Assignees
Labels
design Figure out how we should do something feature size/XL

Comments

@christoferlof
Copy link
Contributor

christoferlof commented Mar 12, 2021

A shared resources used by multiple services may need to be updated.

For example:

  • Firewall rules on the firewall
  • Mirrored packages on the package mirror
  • Workspace app registration by workspace services

Requirements

For the firewall:
As a TRE service integrator
I want an uncomplicated way of enable egress traffic to a Workspace/Workspace Service
So that I can create a bundle that can access the required resources

As an Azure administrator
I want to know which changes to a shared service have been made by which resource
So that I can get an overview of what has made changes

As an Azure administrator
I want changes made to a shared service to be undone when the resource that requires them is uninstalled
So that I I only have the configuration I need

Implementation

High level flow

  1. User submits a POST to create a new resource (eg a VM)
  2. The resource bundle is applied and the VM created
  3. Outputs from the process (eg an IP address) are collected
  4. A message is returned to the API layer with details of which shared resource needs updating, and which values to update (eg a new rule on the shared firewall)
  5. The API layer GETs the shared resource from the data store, merges the changes, and PATCHes it, polling the operation until the shared service is updated.
  6. The original resource operation is completed.

Shared services to-dos

@christoferlof christoferlof added this to the Next milestone Mar 16, 2021
@christoferlof christoferlof modified the milestones: Next, June 2021.1 May 21, 2021
@Lybecker Lybecker mentioned this issue May 27, 2021
@christoferlof christoferlof modified the milestones: June 2021.1, Backlog May 31, 2021
@christoferlof christoferlof modified the milestones: Backlog, June 2021.2 Jun 10, 2021
@christoferlof christoferlof modified the milestone: June 2021.2 Jun 14, 2021
@Lybecker Lybecker removed this from the June 2021.2 milestone Jun 18, 2021
@martinpeck martinpeck added this to the Release 0.3 milestone Jan 17, 2022
@daltskin daltskin moved this to Triage in AzureTRE - Crew Rock Jan 28, 2022
@daltskin daltskin moved this from Triage to In Progress in AzureTRE - Crew Rock Feb 8, 2022
@daltskin daltskin moved this to In Progress in AzureTRE Feature Roadmap Mar 14, 2022
@marrobi marrobi modified the milestones: Release 0.3, Release 0.4 May 27, 2022
@martinpeck martinpeck moved this from In Progress to On Hold in AzureTRE - Crew Rock Jun 8, 2022
@martinpeck martinpeck moved this from On Hold to In Progress in AzureTRE - Crew Rock Jun 14, 2022
@martinpeck martinpeck moved this from In Progress to Done in AzureTRE - Crew Rock Jul 4, 2022
Repository owner moved this from In Progress to Initial Scope Complete in AzureTRE Feature Roadmap Jul 27, 2022
tim-p-allen pushed a commit that referenced this issue Aug 6, 2024
* E2e test number (#23)

* update

* update changelog

* test

* update

* update

* update changelog

* update

* update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Figure out how we should do something feature size/XL
Projects
Status: Initial Scope Complete
Status: Done
Development

No branches or pull requests

6 participants