Skip to content

remove incorrect apostrophe in example#332

Merged
kenyon merged 2 commits intovoxpupuli:masterfrom
wolfaba:patch-1
Nov 22, 2020
Merged

remove incorrect apostrophe in example#332
kenyon merged 2 commits intovoxpupuli:masterfrom
wolfaba:patch-1

Conversation

@wolfaba
Copy link
Copy Markdown
Contributor

@wolfaba wolfaba commented Oct 29, 2020

this yaml code for jira::java_opts with incorrect apostrophe generates with the template JAVA_OPTS="<%= scope.lookupvar('jira::java_opts') %> $JAVA_OPTS" incorrect code

JAVA_OPTS="-Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true'
 $JAVA_OPTS"

which generates then error

/opt/jira/atlassian-jira-software-8.13.0-standalone/bin/catalina.sh: eval: line 517: unexpected EOF while looking for matching `''
/opt/jira/atlassian-jira-software-8.13.0-standalone/bin/catalina.sh: eval: line 519: syntax error: unexpected end of file

In fact, without apostrophe, it still generates linebreak in JAVA_OPTS, and then jira does not start. I will create ticket for this issue.

this yaml code for jira::java_opts with incorrect apostrophe generates with the template JAVA_OPTS="<%= scope.lookupvar('jira::java_opts') %> $JAVA_OPTS" incorrect code 

JAVA_OPTS="-Datlassian.mail.senddisabled=true -Datlassian.mail.fetchdisabled=true -Datlassian.mail.popdisabled=true'
 $JAVA_OPTS"

which generates then error
/opt/jira/atlassian-jira-software-8.13.0-standalone/bin/catalina.sh: eval: line 517: unexpected EOF while looking for matching `''
/opt/jira/atlassian-jira-software-8.13.0-standalone/bin/catalina.sh: eval: line 519: syntax error: unexpected end of file

In fact, without apostrophe, it still generates linebreak in JAVA_OPTS, and then jira does not start. I will create ticket for this issue.
otherwise JAVA_OPTS will be generated with newline and eval will not work in newer Jira as described in issue voxpupuli#333
@kenyon
Copy link
Copy Markdown
Member

kenyon commented Oct 29, 2020

It would be good if we had a test which fails before making this change.

@wolfaba
Copy link
Copy Markdown
Contributor Author

wolfaba commented Oct 30, 2020

It would be good if we had a test which fails before making this change.

@kenyon is this for me to make some fail-test or is it your internal note? Sorry, I'm not profi-puppet, so I have really no idea what to do :(

@kenyon
Copy link
Copy Markdown
Member

kenyon commented Oct 30, 2020

It would be good if we had a test which fails before making this change.

@kenyon is this for me to make some fail-test or is it your internal note? Sorry, I'm not profi-puppet, so I have really no idea what to do :(

@wolfaba this is a note for whoever might want to work on this 😉. To elaborate: if this is really a bug, the tests should have caught it by causing a failure. So if no such failing test exists, that test should be written. Then you can fix the bug and be sure you've fixed it and that it won't reappear without causing a test failure.

@danifr
Copy link
Copy Markdown
Member

danifr commented Nov 22, 2020

I am also affected by this bug. As a workaround I defined all the JAVA_OPTS in a single line

@kenyon kenyon added the docs Improvements or additions to documentation label Nov 22, 2020
@kenyon
Copy link
Copy Markdown
Member

kenyon commented Nov 22, 2020

I just realized that this is just a change to the docs, not the actual code, so disregard my note about tests. Merging. Thanks.

@kenyon kenyon merged commit 8c72691 into voxpupuli:master Nov 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants