/etc/envoy/envoy.yaml file not marked as a config file in deb package

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet

Research direction

Inspect the generated deb package metadata, especially envoy.list and the missing envoy.conffiles entry for /etc/envoy/envoy.yaml. Start by locating the package definition or build entry point that produces these files, then verify that rebuilding the package marks envoy.yaml as a configuration file and preserves it during upgrades.

Written by the indexing model from the issue text.

Description

The /etc/envoy/envoy.yaml is not marked as a config file in the deb packages, which means that updating the package unconditionally overwrites the file.

user@server:/var/lib/dpkg/info$ apt-cache policy envoy | head -2
envoy:
  Installed: 1.36.6
user@server:/var/lib/dpkg/info$ cat envoy.list
/etc
/etc/envoy
/etc/envoy/envoy.yaml
/usr
/usr/bin
/usr/bin/envoy
/usr/share
/usr/share/doc
/usr/share/doc/envoy
/usr/share/doc/envoy/copyright
user@server:/var/lib/dpkg/info$ cat envoy.conffiles
cat: envoy.conffiles: No such file or directory
user@server:/var/lib/dpkg/info$
Dominant language
Starlark
Stars
1
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/apt

All issues in envoyproxy/apt

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.