Extra settings:

Custom volume and volume mount options:

@kurokobo Thank you for contributing these docs!

As an aside, it would be nice to make this easier for users. Maybe we could add a settings_file_configmap parameter that would automatically mount the contents of the configmap specified into the respective containers.

Generally, we try not to add unnecessary new parameters, but this is a common enough use case and would say users the trouble of double quotes issues on values for the existing extra_settings param implementation.

What do you think about that idea?

@rooftopcellist
Hi, thanks for reviewing and merging.

As an aside, it would be nice to make this easier for users. Maybe we could add a settings_file_configmap parameter that would automatically mount the contents of the configmap specified into the respective containers.

Yes, this is exactly one of the things I was going to draft as an RFE. I already made quick investigation and it seems to that perhaps we can implement almost same things on Galaxy Operator and EDA Server Operator as well.
On both galaxy_ng and eda-server, there are no predefined configuration directory (like /etc/tower/conf.d for AWX), but both of them already have django-split-settings that can include multiple files into main settings file. So I didn't test at all, but I think,

• For Galaxy Operator. we may be able to add include to load custom settings files into settings.py that generated by Galaxy Operator
• For EDA Server Operator, we may be able to define EDA_SETTINGS_FILE with a python file that generated by EDA Server Operator that contains include

For now, let me make an RFE for AWX Operator.