Skip to content

Destroy and recreate service bus in Tre stop start scripts#4883

Draft
JC-wk wants to merge 15 commits intomicrosoft:mainfrom
JC-wk:tre-stop-start
Draft

Destroy and recreate service bus in Tre stop start scripts#4883
JC-wk wants to merge 15 commits intomicrosoft:mainfrom
JC-wk:tre-stop-start

Conversation

@JC-wk
Copy link
Collaborator

@JC-wk JC-wk commented Mar 6, 2026

Resolves #3953

What is being addressed

When make tre-stop runs destroy the service bus and stop function apps / web apps (to prevent log spam) to save costs.
Update: See additonal logging costs (right of chart) if the apps are not stopped
image

How is this addressed

  • Update control_tre to remove the service bus and stop related components
  • Update documentation
  • Update CHANGELOG.md

By including the terraform apply in the start script it allows a wider variety of things to be stopped / deleted and then recreated to save costs.

@JC-wk JC-wk requested a review from a team as a code owner March 6, 2026 15:16
@github-actions
Copy link

github-actions bot commented Mar 6, 2026

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit f0771b8.

♻️ This comment has been updated with latest results.

@JC-wk
Copy link
Collaborator Author

JC-wk commented Mar 6, 2026

Thoughts @marrobi ? Adding the TF apply this becomes more similar to make tre-deploy. Do you think the service bus destroy should be an optional param that users can run, and then they can run make tre-deploy first then tre-start to restart their TRE instead? Happy to amend this as necessary.

@JC-wk JC-wk marked this pull request as draft March 9, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'Service Bus Namespace' Continues Running Even After $ make tre-stop

2 participants