-
Notifications
You must be signed in to change notification settings - Fork 37
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
apim-certs.yaml prevents successful helm upgrade
#152
Comments
This should be fixed in the If so, it's weird, as it should be in there. Will investigate, thanks for reporting! |
For the sake of completeness, here's the fix (from September): |
I was using the 0.12.1 branch. I'll make the changes locally while I use this branch. I'll return to the 1.0 branch in a little bit. Thanks for the fix! |
The 0.12.1 branch does not contain the |
No, I was just trying a vanilla 0.12.1 helm install, just to play around.
I'll return to the 1.0 beta helm install once I get 0.12.1 running
happily. It looked like the 1.0 beta was going to need some work on the
helm install, so I figured I'd make sure I could get the 0.12.1 version
running before I moved ahead. Just trying one thing at a time.
ᐧ
…On Sat, Jan 5, 2019 at 11:37 AM Martin Danielsson ***@***.***> wrote:
The 0.12.1 branch does not contain the portal-auth component, so beware
of that, if you're trying to use the old helm chart with the new beta.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfD8CitSi5d786-erd7y4ws5Y6AIAe6ks5vAP77gaJpZM4Zovo6>
.
|
Looks like
apim-certs.yaml
falls prey to the same issue as reported here:If I understand it correctly, a comment followed by a variable will ignore the variable and the following line, too. This isn't
apim-certs.yaml
's fault, but it preventshelm upgrade
from running. An upgrade will return this error:SImply moving the
apim-certs.yaml
out of thetemplates
directory will solve the issue, but if you actually want to run that template, you're out of luck at the moment.I'll see if I can find a fix for it.
The text was updated successfully, but these errors were encountered: