extra_settings in awx-operator

Archives AWX Project
1

tl;dr

I’m trying to use the extra_settings parameter in the awx-operator (https://github.com/ansible/awx-operator#extra-settings) but I’m having trouble getting it to lay down a settings whose value should be a string when it gets to /etc/tower/settings.py
Has anyone else had success forcing extra_settings values to be strings or is this a general bug in the operator?

Full story:

I’m testing adding a new setting to awx, but I imagine this would happen with any setting – awx PR is https://github.com/ansible/awx/pull/11395/files

So in my CR to create awx added the following:

extra_settings: - setting: DEFAULT_EXECUTION_QUEUE_POD_SPEC_OVERRIDE value: “MY_PRETTY_YAML_PODSPEC_OVERRIDE”
but then when I look at /etc/tower/settings.py inside the container, looks to me like this would not parse (because its supposed to be a python file, and the value is not in quotes)

$ cat settings.py | grep POD_SPEC

DEFAULT_EXECUTION_QUEUE_POD_SPEC_OVERRIDE = MY_PRETTY_YAML_PODSPEC_OVERRIDE

I want the value “MY_PRETTY_YAML_PODSPEC_OVERRIDE” to be a string by the time it lands in /etc/tower/settings.py

2

Could you escape the values in YAML?
Testing with python YAML suggests that:

value: “‘MY_PRETTY_YAML_PODSPEC_OVERRIDE’”

should work.

Looking at the operator, I do see how this doesn’t do anything for you when it comes to strings:

https://github.com/ansible/awx-operator/blob/ebe5d1e2f4afd7fd329c18420947ff5840670293/roles/installer/templates/config.yaml.j2#L93

to better help out, I guess we would have to have some type designator.