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
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
I tried to use semantic versions range in my charts version. It does work at first (the correct version are deployed) but then on the next run, landscaper will always see a difference and run an update.
For example:
In our yaml file we have chart: local/hello-world:^0.1.0
We run landscaper apply and hello-world:0.1.0 is installed (it could also install 0.2.0 and we would have the same problem)
Next time we run landscaper we have an output similar to this:
And then an update would be triggered but it shouldn't since the same version would be installed.
To fix that I think that landscaper needs to find the actual version from the semantic version range and use that for the comparison.
The text was updated successfully, but these errors were encountered:
I tried to use semantic versions range in my charts version. It does work at first (the correct version are deployed) but then on the next run, landscaper will always see a difference and run an update.
For example:
In our yaml file we have chart:
local/hello-world:^0.1.0
We run landscaper apply and hello-world:0.1.0 is installed (it could also install 0.2.0 and we would have the same problem)
Next time we run landscaper we have an output similar to this:
And then an update would be triggered but it shouldn't since the same version would be installed.
To fix that I think that landscaper needs to find the actual version from the semantic version range and use that for the comparison.
The text was updated successfully, but these errors were encountered: