Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Landscaper not evaluating semantic range before comparing versions #105

Open
royjs opened this issue Nov 2, 2017 · 0 comments
Open

Landscaper not evaluating semantic range before comparing versions #105

royjs opened this issue Nov 2, 2017 · 0 comments

Comments

@royjs
Copy link
Contributor

royjs commented Nov 2, 2017

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:

--- Current test-hello-world
+++ Desired test-hello-world
@@ -2,7 +2,7 @@
   "name": "test-hello-world",
   "namespace": "test",
   "release": {
-    "chart": "hello-world:0.1.0",
+    "chart": "hello-world:^0.1.0",

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants