Parameterization of the client_max_body_size directive in Nginx

[shellclear]

SUMMARY

This commit aims to parameterize an Nginx configuration that is currently hardcoded to 5M, causing issues with file uploads.

ISSUE TYPE

• New or Enhanced Feature

ADDITIONAL INFORMATION

With this change, it will be possible to set the value of the client_max_body_size directive during the creation of the AWX CR or modify an existing AWX instance running in the cluster.

The default value for the directive remains 5M.

apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: example-awx1
  namespace: awx
spec:
  nginx_client_max_body_size: 10

[shellclear]

#2013

[fosterseth]

@rooftopcellist I believe this is configurable through the AAP installer, so maybe makes sense to allow it here too

[rooftopcellist]

I agree this should be added, and I fully expect the diff here to work. But I am torn because this same param is configurable in galaxy-operator, but there it is type string not an int that expects the "M" units on the end to be passed on the string.

I think what you have here in this PR is the better approach, but the inconsistency across ansible operators may be confusing.

We plan to create a new apiVersion for all of these operators to make a consistent parameter interface. When we do, we should modify the galaxy-operator to use this approach (int and adding on the units in the template).

[rooftopcellist]

@fosterseth If you agree with this, feel free to merge next week.

[shellclear]

I agree this should be added, and I fully expect the diff here to work. But I am torn because this same param is configurable in galaxy-operator, but there it is type string not an int that expects the "M" units on the end to be passed on the string.

I think what you have here in this PR is the better approach, but the inconsistency across ansible operators may be confusing.

We plan to create a new apiVersion for all of these operators to make a consistent parameter interface. When we do, we should modify the galaxy-operator to use this approach (int and adding on the units in the template).

for me, it needs to be an integer. I'll push a new PR to change the parameter in the galaxy-operator so that we can keep the operator aligned.