-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add possibility to control dapr version #32
Comments
Thanks @dennishog. We will provide more details on Dapr and KEDA versions management soon. |
Hi @torosent, @BigMorty: What about its progress? Any ETA for it? I have the same idea with @dennishog and would like to use the same Dapr version for all the development to a staging environment, it will limit an error-prone when developing the real application. |
@kendallroden, any update on this? |
we are only upgrading dapr today on behalf of, we are not providing the capability of version pinning and it has not been designed |
what happen to azure container environments created with a certain dapr version? are those automatically updated or a new azure container environment has to be created? |
+1 on this. As we are heavily dependent on Dapr, we have some versions (e.g. 1.12.3) on which we can rely on using AKS. |
+1 What happens when a Dapr 2.0 with breaking changes is released? Does everyone have to deploy their updated applications at the exact time that Azure decides to migrate the environment? |
@greenie-msft has an update on this. Please share! |
Add possibility to control the version of dapr used by environment and containerapp.
We want to be able to use the same version in all our environments, as well as our local docker-compose development environment.
Great work on container apps! 👍
The text was updated successfully, but these errors were encountered: