Skip to content

Airlock should support dynamic resource suffix #3237

Open
@eladiw

Description

Description

As a TRE Administrator developer
I want to make sure that when the resources suffix will be dynamic (i.e. won't always be 4 chars) the airlock processor will be able to find target resources
So that it will continue to function

Acceptance criteria

  • airlock processor should not assume the storage account suffix, but get it from the message itself

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    storyStories are the smallest unit of work to be done for a project.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions