Open ytimocin opened 1 month ago
:wave: @ytimocin Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Overview of feature request
We can have a command that would allow users to export all the details of a Radius environment in a file so that it could be used for disaster recovery and migration purposes.
Ex:
rad env export my-env
Ans:my-env.bicep is generated.
Acceptance criteria
rad env export my-env
we can get all the details of a Radius environment to a file.rad env import my-env.bicep
orrad deploy my-env.bicep
we can get the same environment up and running in a completely different cluster with no problems.Additional context
This was discussed in the Design Meeting on 9th of July 2024.
Would you like to support us?
AB#12672