Why squid is removed from the repo?

[nnWhisperer]

Hello,

1. Looking at the blueprints, I saw about squid. It seems like a good solution to limit egress calls to other domains. I wonder, why have this been moved to a folder called __need_fixing and commented out?
2. If the reason is that google provides an alternative service for filtering to squid proxy and saw it as a rival service, then, what is that service we can use instead of squid?
   

[wiktorn]

ad 1. It was moved to _need_fixing here #1936, and the rationale was that the repository was no longer available. Later is was removed in #2131
ad 2. You can now use Secure Web Proxy as an alternative to Squid proxy. There is also a module to help you deploy it - modules/net-swp

[nnWhisperer]

Which repository was no longer available?

[nnWhisperer]

@wiktorn , thank you for your response, could you tell me that which repository was no longer available? I see that squid repository still exists in github? Thank you in advance.

[wiktorn]

Container Registry repository that was used to publish the Docker image gcr.io/pso-cft-fabric is no longer available, and there are no plans to expose container images as a part of Fabric FAST project.

[nnWhisperer]

Not to expose the container images as part of the fabric, but I guess adding a code to use the cloud build trigger module to generate the image from the Dockerfile might have been another solution though. I guess the main reason is about the presence of the secure web proxy in gcp, starting with the removal of the image hosted on the gcr.io in the first place and then removing the feature here. Thank you.