Key retrieval not covered by apt-proxy settings in juju
Bug #1707070 reported by
Jason Hobbs
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Elasticsearch Charm |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
While installing the package is covered by juju's apt-http-proxy and apt-https-proxy settings, retrieving the key is not.
It would be a lot nicer if the charm had a config setting for the key, and included the key as the default setting.
Right now to work around this, I have to host the key internally somewhere on my network.
tags: | added: cdo-qa cdo-qa-blocker |
tags: | added: foundations-engine |
no longer affects: | elasticsearch (Juju Charms Collection) |
Changed in elasticsearch-charm: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: field-medium |
Changed in charm-elasticsearch: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
Looks like this is an upstream bug report: /github. com/ansible/ ansible/ issues/ 31691
https:/