8000 Yaml Parser fails to parse ansible configuration files · Issue #17068 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

Yaml Parser fails to parse ansible configuration files #17068

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.

Sign up for GitHub

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

Jump to bottom
Closed
bburnichon opened this issue Dec 18, 2015 · 4 comments
Closed

Yaml Parser fails to parse ansible configuration files #17068

bburnichon opened this issue Dec 18, 2015 · 4 comments
Labels
Bug Status: Needs Review Yaml

Comments

@bburnichon
Copy link
Contributor

I don't know whether ansible is not YAML standard compliant, but a valid yaml configuration like:

---
- name: ensure timezone is set in apache2 php.ini
  lineinfile: dest=/etc/php5/apache2/php.ini
              regexp='date.timezone ='
              line='date.timezone = {{ server.timezone }}'

is not accepted as valid. This makes http://insight.sensiolabs.com complains and declaring many critical violations.

I tested this with www.yamllint.com and there are no issues.
@xabbuh
Copy link
Member
xabbuh commented Dec 18, 2015

What exceptions do you get?

@bburnichon
Copy link
Contributor Author

Don't really know. Insight support told me they use symfony yaml parser component.

@xabbuh
Copy link
Member
xabbuh commented Dec 19, 2015

This indeed looks like a bug to me. The error message is:

Unable to parse at line 4 (near " regexp='date.timezone ='").

@xabbuh
Copy link
Member
xabbuh commented Dec 28, 2015

closing as a duplicate of #11109

@xabbuh xabbuh closed this as completed Dec 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Status: Needs Review Yaml
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xabbuh @bburnichon @carsonbot
0