flexible print configuration

[jwkaltz]

Follow-up to PR #631:
Be able to flexibly choose print configuration for XML2PDF or for MapFish-Print.

[pfirpfel]

• the variable is not getting passed correctly yet

If you mean from Makefile to the rendered template, this also does not work for stuff like PG_USER/PG_PASSWORD.

.venv/bin/create_standard_yaml
.venv/bin/create_standard_yaml -p MapFishPrint
.venv/bin/create_standard_yaml -p XML2PDF

Work all fine.

[vvmruder]

For me this adds ways too much layers of complexity. Why not simply document the selectable print proxy and thats it.

Every user should be perfectly able to setup this in his pyramid oereb YAML. I don't think this helps anybody. Since user names and tokens need to be specified anyhow.

[jwkaltz]

For me this adds ways too much layers of complexity. Why not simply document the selectable print proxy and thats it.

Every user should be perfectly able to setup this in his pyramid oereb YAML. I don't think this helps anybody. Since user names and tokens need to be specified anyhow.

This PR is the follow-up to #631 (comment)

I am not sure to understand your concern. For the user, nothing changes, s/he simply has an additional option when using the scripts to define which print backend s/he wants to use. If s/he does not use this option, there is a default. I don't see how this adds complexity, isn't this analog to the other configuration options?

[vvmruder]

In this comment I clearly point out my suggestions to leave it as integration problem.

I think adding all the possible options a config yaml could look like we will end up in a fairly complex environment. And I want to keep it simple as possible. As I said: At least the credential need to be filled in later by hand.

And the standard configuration should only act as a starting point. All customisation will be done by hand later.

[voisardf]

Looks good to me, thanks