get_aws_ecr_credentials playbook expects docker_http_proxy

[Joseph Richard]

Brief Description
-----------------
when sysinv runs ansible playbook to push docker images, get_aws_ecr_credentials.yml fails if no docker_http_proxy is configured

Severity
--------
Provide the severity of the defect.
Likely minor, but unknown what side-effects this is having from other playbooks not applying in sysinv kube_app section. platform-integ-apps isn't applied.

Steps to Reproduce
------------------
Configure aws docker registry without docker_http_proxy.

Expected Behavior
------------------
All playbooks apply successfully

Actual Behavior
----------------
get_aws_ecr_credentials fails to apply.

Reproducibility
---------------
Seems consistent in this config

Timestamp/Logs
--------------
fatal: [localhost]: FAILED! => {"msg": "The field 'environment' has an invalid value, which includes an undefined variable. The error was: 'docker_http_proxy' is undefined\n\nThe error appears to have been in '/usr/share/ansible/stx-ansible/playbooks/roles/common/push-docker-images/tasks/get_aws_ecr_credentials.yml': line 11, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: Get the {{ registry.name }} credentials\n ^ here\nWe could be wrong, but this one looks like it might be an issue with\nmissing quotes. Always quote template expression brackets when they\nstart a value. For instance:\n\n with_items:\n - {{ foo }}\n\nShould be written as:\n\n with_items:\n - \"{{ foo }}\"\n"}

Workaround
----------
Manually apply platform-integ-apps.

[Ghada Khalil (gkhalil)]

Marking as low priority since this deals with a very specific config which is not widely used in the stx community

[Ramaswamy Subramanian (rsubrama)]

No progress on this bug for more than 2 years. Candidate for closure.

If there is no update, this issue is targeted to be closed as 'Won't Fix' in 2 weeks.

[John Kung (john-kung)]

As per prior comment, now Closed as Won't Fix