Closed ibexa-yuna closed 1 year ago
Thanks for reporting this!
The only place I can find that uses the newer bash syntax [[
and ]]
is in ddev-redis; it's not used in ddev-platformsh:
if [[ $DDEV_PROJECT_TYPE != drupal* ]] || [[ $DDEV_PROJECT_TYPE =~ ^drupal(6|7)$ ]] ;
then
exit 0
fi
And I haven't figured out why that would fail, but I can recreate your situation.
I was able to track and "fix" it, looks like it's a problem of data sanitation during output:
https://github.com/ibexa-yuna/ddev-platformsh/commit/c8951cf3462a9446e2de4ae5aacd28ff0e0b7560
Just removing a comment fixes it? And then... why does this work so many other places and not with your .platform.app.yaml. I think we've on the verge of finding out!
PR is welcome! Also, we could add the ibexa type to tests if you'd like.
not with your .platform.app.yaml
SOLR p.sh service requires some multiline input string as parameters, which is what we can see during the error:
# echo service_def=map[configuration:map[configsets:map[mainconfig:configsets/solr6] cores:map[collection1:map[core_properties:configSet=mainconfig
schema=schema.xml
]] endpoints:map[collection1:map[core:collection1]]] disk:412 fulltype:solr:7.7 type:solr version:7.7]
Hey @rfay
Would you like me to submit a PR or this is something that can be fixed on your end in a more elegant way, than just cutting comments out?
A PR removing the "comment" would be fine, or fixing the comment would be fine as well. If you're able to provide a trivial example that breaks this that would be helpful as well.
IIRC the "comment" is actually documentation in the generated config, so it only appears to be a comment in this context. But I'm also sure we can live without it.
Thanks so much!
Hi Randy,
I've created a PR for this: https://github.com/ddev/ddev-platformsh/pull/108
Thanks!
Hi,
I'm using my project that's already running on Platform.sh. This is my .platform.app.yaml.
The error I'm getting is:
$ ddev get ddev/ddev-platformsh
If I try installing ddev-redis manually it's installing without a problem, which leads me to believe that the problem is in ddev-platformsh.
If I run the installation with
-v
then I can see definitely something wrong with bash in regards to schema.xml:This schema.xml reference is coming from my services.yaml.
Steps to reproduce:
ddev get ddev/ddev-platform.sh
, answer script questions, observe the error