-
Notifications
You must be signed in to change notification settings - Fork 802
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
{# comments #} replaced with # comments #618
Conversation
I got faulty YAML when running a helm upgrade, perhaps they are a mistake?
The one difference between these two is that the plain I'm not opposed to this :) Does this fix the issue, @consideRatio? |
Ah yes it did for me, but okay so then we might need to add something like I'll try! |
BTW; googling for this was tough, what are good keywords? Got an URL or similar to read about these kinds of comments? |
I tried the following combinations, only normal comment option avoided the
|
Yeah, it's pretty difficult. I knew this from reading
https://golang.org/pkg/text/template/ (and other resources on searching for
'go templates', which is what helm templates are). Perhaps things to add to
our contributing.md?
…On Sat, Mar 31, 2018 at 8:30 PM, Erik Sundell ***@***.***> wrote:
BTW; googling for this was tough, what are good keywords? Got an URL or
similar to read about these kinds of comments?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#618 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB23o0arsfFCcHBli1IrZxezE2XGzwVks5tkEnogaJpZM4TCshy>
.
--
Yuvi Panda T
http://yuvi.in/blog
|
Oh wow, the syntax is actually `{{/* */}}`. Maybe that's why you are
getting indent errors? {# #} is valid Jinja2 syntax I think, but *not*
valid go template syntax.
…On Sat, Mar 31, 2018 at 8:23 PM, Erik Sundell ***@***.***> wrote:
A simple syntax error with a simple fix - I think! In this PR I simply
replaced {# these types of comments #} with # these types of comments.
Perhaps {# this comment syntax #} is valid, but if so it seem to have
caused some indentation errors. I got an error on my helm upgrade ...
command that appears to be commonly associated with indentation issues.
Error:
UPGRADE FAILED:
YAML parse error on z2jh-extended/charts/jupyterhub/templates/hub/deployment.yaml:
error converting YAML to JSON: yaml: line 111: could not find expected ':'
Ping #597 <#597>
@mattjbray <https://github.com/mattjbray> @yuvipanda
<https://github.com/yuvipanda>
------------------------------
You can view, comment on, or merge this pull request online at:
#618
Commit Summary
- Comments {# #} replaced with #
File Changes
- *M* jupyterhub/templates/hub/deployment.yaml
<https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/618/files#diff-0>
(4)
Patch Links:
- https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/618.patch
- https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/618.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#618>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB23rGcwpJH7oheJel9h4KUzi1S0X2xks5tkEg1gaJpZM4TCshy>
.
--
Yuvi Panda T
http://yuvi.in/blog
|
Yepp! I saw it actually was |
LGTM, Thanks for the PR! |
@yuvipanda ❤️ |
A simple syntax error with a simple fix - I think! In this PR I simply replaced
{# these types of comments #}
with# these types of comments
.Perhaps
{# this comment syntax #}
is valid, but if so it seem to have caused some indentation errors. I got an error on myhelm upgrade ...
command that appears to be commonly associated with indentation issues.Error: UPGRADE FAILED: YAML parse error on z2jh-extended/charts/jupyterhub/templates/hub/deployment.yaml: error converting YAML to JSON: yaml: line 111: could not find expected ':'
Ping #597 @mattjbray @yuvipanda