Ubuntu: ‘Connection to the Snap Store failed’ during upgrade from Ubuntu 20 to 22.

Bash: using dig for reverse DNS lookup by IP.

Kubernetes: list all pods in deployment.

GKE: Determine Anthos on-prem GKE master node and IP address.

Terraform: migrate state from local to remote Google Cloud Storage bucket and back.

Python: fixing ‘CryptographyDeprecationWarning: Blowfish has been deprecated’.

Ubuntu: A centralized apt package cache using squid-deb-proxy.

Ubuntu: Enabling the Ubuntu universe Repository.

Ansible: installing the latest Ansible on Ubuntu.

Ubuntu: install latest git client from PPA to fix ‘unsafe repository’ errors.

Stackoverflow, using add-apt-repository and apt-key with proxyī, determining key from ppa pageī, ansible and apt with proxy

The key id used is the one published on the ansible ppa page. The same type of advice goes toward apt-key, it does not automatically use the proxy configured for apt-get, you need to use the ‘http-proxy’ parameter parameter similar to below. Sudo -E apt-add-repository -yes -update ppa:ansible/ansible export http_proxy= export https_proxy= # preserve environment sent to sudo Instead, you need to set the standard http_proxy/https_proxy variables, and use “sudo -E” to preserve the environment if using sudo. You might be tempted to believe that if you have configured “apt-get” with a proxy, then apt-add-repository would look at those settings – it will not! Using the Ansible ppa as an example, the command from the documentation is: sudo apt-add-repository -yes -update ppa:ansible/ansible

In a production environment where a proxy such as squid is necessary to reach the public internet, you may need use apt-add-repository to install a package from a ppa.

Apt add repository