Sumologic Cleanup fails with tcp: dial tcp: lookup '': no such host error

[ib-ak]

Describe the bug A clear and concise description of what the bug is.

cleanup.sh is looking for HTTP_PROXY = ''(single-quotes) instead of assigning it null/blank value.

Logs Logs which can be helpful in investigating the issue.

Initializing the backend...

Initializing provider plugins...
- Reusing previous version of sumologic/sumologic from the dependency lock file
- Reusing previous version of hashicorp/kubernetes from the dependency lock file
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
│ sumologic/sumologic: could not connect to registry.terraform.io: Failed to
│ request discovery document: Get
│ "https://registry.terraform.io/.well-known/terraform.json": proxyconnect
│ tcp: dial tcp: lookup '': no such host
╵

╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
│ hashicorp/kubernetes: could not connect to registry.terraform.io: Failed to
│ request discovery document: Get
│ "https://registry.terraform.io/.well-known/terraform.json": proxyconnect
│ tcp: dial tcp: lookup '': no such host
╵

Command used to install/upgrade Collection Direct command which you used to install/upgrade collection.

Configuration Configuration used for Collection e.g. user-values.yaml for helm.

default values.yaml

To Reproduce Steps to reproduce the behavior.

1. Install sumo logic chart
2. Delete the installed helm chart

Expected behavior A clear and concise description of what you expected to happen.

1. Helmchart should be uninstalled.

Environment (please complete the following information):

• Collection version (e.g. helm ls -n sumologic):
• Kubernetes version (e.g. kubectl version): 1.24
• Cloud provider: AWS
• Others:

Fix:

Update cleanup.sh similar to the value in setup.sh. Change single quotes to double quotes

setup.sh

sumologic-kubernetes-collection/deploy/helm/sumologic/conf/setup/setup.sh

Lines 45 to 47 in 3a613a2

	export HTTP_PROXY=${HTTP_PROXY:=""}
	export HTTPS_PROXY=${HTTPS_PROXY:=""}
	export NO_PROXY=${NO_PROXY:=""}

cleanup.sh

sumologic-kubernetes-collection/deploy/helm/sumologic/conf/cleanup/cleanup.sh

Lines 8 to 10 in 3a613a2

	export HTTP_PROXY="${HTTP_PROXY:=''}"
	export HTTPS_PROXY="${HTTPS_PROXY:=''}"
	export NO_PROXY="${NO_PROXY:=''}"

Anything else do we need to know Add any other context about the problem here, e.g. issue happens only occasionally.