Merge pull request ansible#12778 from keithjgrant/12542-schedule-exce…

…ptions

Schedule exceptions

Merge pull request ansible#12552 from whitej6/jlw-generic-oidc

Implement Generic OIDC Provider

Merge pull request ansible#12609 from john-westcott-iv/oracle_awx_tri…

…age_reply

Adding triage response for inquaries around Oracles version of AWX

Merge pull request ansible#12505 from sarabrajsingh/bugfix/add-setupt…

…ools-scm-dependency-to-workflow

added setuptools-scm dependency to promote.yml workflow

Merge pull request ansible#12391 from AlanCoding/compose_graphs

Do the grafana thing in docker-compose templating itself

Merge pull request ansible#12240 from fosterseth/make_prometheus_grafana

Add prometheus and grafana make commands for local environment

Merge pull request ansible#12096 from rooftopcellist/localization-dev…

…el-4-24

Localization Update & Add KO to supported languages

Merge pull request ansible#11979 from nixocio/ui_move_boolean

Move AWX_MOUNT_ISOLATED_PATHS_ON_K8S to be closer to other booleans

Disable checkbox while job is running in project and inventory source…

… lists (ansible#11841)

Fixup conversion of memory and cpu settings to support k8s resource r…

…equest format (ansible#11725)

fix memory and cpu settings to suport k8s resource request format

* fix conversion of memory setting to bytes

This setting has not been getting set by default, and needed some fixing
up to be compatible with setting the memory in the same way as we set it
in the operator, as well as with other changes from last year which
assume that ansible runner is returning memory in bytes.

This way we can start setting this setting in the operator, and get a
more accurate reflection of how much memory is available to the control
pod in k8s.

On platforms where services are all sharing memory, we deduct a
penalty from the memory available. On k8s we don't need to do this
because the web, redis, and task containers each have memory
allocated to them.

* Support CPU setting expressed in units used by k8s

This setting has not been getting set by default, and needed some fixing
up to be compatible with setting the CPU resource request/limits in the
same way as we set it in the resource requests/limits.

This way we can start setting this setting in the
operator, and get a more accurate reflection of how much cpu is
available to the control pod in k8s.

Because cpu on k8s can be partial cores, migrate cpu field to decimal.

k8s does not allow granularity of less than 100m (equivalent to 0.1 cores), so only
store up to 1 decimal place.

fix analytics to deal with decimal cpu

need to use DjangoJSONEncoder when Decimal fields in data passed to
json.dumps