Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to retrieve the updated configuration from the debug endpoint with the watcher flag enabled. #89

Open
Tirth7545 opened this issue Sep 9, 2024 · 0 comments
Labels
bug Something isn't working needs investigation It looks as though have all the information needed but investigation is required

Comments

@Tirth7545
Copy link

Tirth7545 commented Sep 9, 2024

Description :

  • While running a custom build of red-panda-connect with the watcher flag enabled in debug mode and trying to retrieve the latest configuration from the debug endpoint.
  • The documentation (REF) states that the following endpoints should provide the current configuration:
    • /debug/config/json returns the configuration in JSON format
    • /debug/config/yaml returns the configuration in YAML format

However, after updating the configuration file, these endpoints still return the older configuration Instead It Should Return the latest configuration which red-panda-connect is using.

How To Reporduce

  • create one config.json file. (you can use yaml as well)
   "http":{
       "enabled": true,
       "address": "0.0.0.0:4195",
       "root_path": "/benthos",
       "debug_endpoints": true
   },
 "input": {
   "generate": {
     "count": 100,
     "mapping": "root = \"hello\""
   }
 },
 "output": {
   "stdout": {
     "codec": "lines"
   }
 },
 "pipeline": {
   "processors": [
     {
       "mapping": "root.data = \"xyzza\"\n root.abc = \"abcd\""
     }
   ]
 }
}
  • Run rpk file with this command rpk connect run -c temp.json --w
  • Execute Below curl command
curl --location 'http://0.0.0.0:4195/benthos/debug/config/json
  • Now done some change in above mentioned file
  • Re run the above curl command

Expectation

  • When the user executes the curl command a second time, it should return the latest configuration. However, it is currently returning the older configuration.
@mihaitodor mihaitodor added bug Something isn't working needs investigation It looks as though have all the information needed but investigation is required labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs investigation It looks as though have all the information needed but investigation is required
Projects
None yet
Development

No branches or pull requests

2 participants