Open willtsai opened 2 weeks ago
:wave: @willtsai 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
Today, the
rad run app.bicep
command does not restart the pods for the application. Thus, if a user makes a change to their resource (e.g. Dapr pub/sub component) and then runsrad run app.bicep
again, the pod may not have picked up the configuration changes made to the resource without the pod being restarted as well. This means that the user would then have to manually restart their pod(s) withkubectl rollout restart
in addition to therad run app.bicep
command.This request is for a convenience feature where a flag (or equivalent) can be optionally set in the
rad
CLI for therad run
andrad deploy
commands that will trigger pod restarts in addition to deploying and running the application.Acceptance criteria
rad run
andrad deploy
commands that would trigger pod restarts (similar to manually runningkubectl rollout restart
) in addition to deploying and running the application.Additional context
Some additional details about Kubernetes pod restarts: https://last9.io/blog/how-to-restart-kubernetes-pods-with-kubectl-tutorial/
Would you like to support us?
AB#12576