You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Publishing a new version of a trait and rerunning the application doesn't pick up the latest version of a trait
To Reproduce
Steps to reproduce the behavior:
Create a trait
Create an application using the trait
Update the trait
Rerun the application deployment 'vela up -f myapp.yaml'
Expected behavior
The latest version of the trait should be applied as per the docs "If no revision is specified for a definition, KubeVela will use the latest revision available at evaluation time. This will usually be the next time you upgrade your application."
Screenshots
KubeVela Version
1.9.8
Cluster information
Kubernetes Version v1.25.11
Additional context
The text was updated successfully, but these errors were encountered:
If you require the latest and don't want explicit versioning use a unique parameter that is always updating (a timestamp) that is passed to the definitions all the time, that will refresh it. I've used a timestamp that is passed in the definition labels and keeps the version current.
Describe the bug
Publishing a new version of a trait and rerunning the application doesn't pick up the latest version of a trait
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The latest version of the trait should be applied as per the docs "If no revision is specified for a definition, KubeVela will use the latest revision available at evaluation time. This will usually be the next time you upgrade your application."
Screenshots
KubeVela Version
1.9.8
Cluster information
Additional context
The text was updated successfully, but these errors were encountered: