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

[Story] Deploy bundles to a TRE workspace on message arrival #483

Closed
7 tasks done
Tracked by #18
adishachar opened this issue Jul 20, 2021 · 5 comments
Closed
7 tasks done
Tracked by #18

[Story] Deploy bundles to a TRE workspace on message arrival #483

adishachar opened this issue Jul 20, 2021 · 5 comments
Assignees
Labels
story Stories are the smallest unit of work to be done for a project.
Milestone

Comments

@adishachar
Copy link

adishachar commented Jul 20, 2021

Description

As a TRE user
I want resources to be provisioned as Azure resources upon message retrieval from message queue.

Acceptance criteria

@adishachar adishachar added the story Stories are the smallest unit of work to be done for a project. label Jul 20, 2021
@adishachar adishachar added this to the Next milestone Jul 20, 2021
@adishachar adishachar changed the title Actually create VM service within a workspace Deploy and Release Azure resources for VM service associated to a TRE workspace Jul 20, 2021
@adishachar adishachar changed the title Deploy and Release Azure resources for VM service associated to a TRE workspace [Story] Deploy and Release Azure resources for VM service associated to a TRE workspace Jul 20, 2021
@adishachar
Copy link
Author

Not required with current ADR.

@adishachar adishachar reopened this Jul 27, 2021
@adishachar adishachar changed the title [Story] Deploy and Release Azure resources for VM service associated to a TRE workspace [Story] Deploy bundles to a TRE workspace on message arrival Jul 27, 2021
@marrobi marrobi modified the milestones: Next, Release 0.2 Jul 28, 2021
@TessFerrandez
Copy link
Member

Is this a task from some bigger story? Who is sending a message for the message queue to handle? what are the specs of said message?

@adishachar
Copy link
Author

@TessFerrandez , yes, it is part of virtual desktop story #18

@TessFerrandez
Copy link
Member

TessFerrandez commented Aug 3, 2021

@adishachar I believe #18 is a feature, not a story, but the feature links to both tasks and other stories as if it was some type of hybrid story. Perhaps we can clean things up and break out an appropriate story from the #18 feature to move the tasks that currently link from #18, and also remove the story label from this issue, as well as the milestone, and link it from an appropriate story.

@adishachar
Copy link
Author

@TessFerrandez #18 is indeed a feature and not a story (and has the label 'feature').
It has 9 issues under it - 8 are stories and only one, #490, which is the ADR, was define as 'task'.
Since the ADR is already done and close, i dont see much point to change it now for a 'story'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Stories are the smallest unit of work to be done for a project.
Projects
None yet
Development

No branches or pull requests

5 participants