A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

Vector could bind the the wrong port during reloading when api.address is updated. To reproduce:

• start vector without api.enabled=true
• update config to have

  • api:
      enabled: true
      address: 127.0.0.1:18686
    

• vector will reload and start the service, however the server is bind to port 8686 (the default) port

if then set api.enable: false, trigger reload, again set api.enable:true and trigger reload, the api server will then be bind to the correct port.

I think somehow vector is using the old config for the server config

Configuration

initial config:

# not actually set, below are default values
# api:
#   enabled: false
#   address: 127.0.0.1:8686

enable api server on port 18686

api:
  enabled: true
  address: 127.0.0.1:18686

Version

0.54

Debug Output

Example Data

No response

Additional Context

No response

References

No response