You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
import --watch ignores --config on file changes and can upload to the wrong server #628
When using import --watch with a custom --config, the initial import uses the specified configuration, but subsequent imports triggered by file changes use the default configuration.
If both configurations contain the same context name pointing to different servers, updates are uploaded to a different server from the initial import.
Expected behavior
The initial import and all subsequent watched imports should resolve the context using the configuration selected with --config.
Actual behavior
The initial import uses the selected configuration. Watched imports resolve the same context name using the default configuration and therefore upload to the other server.
Confirm that Watch Config Demo version 1.0 appears on http://localhost:8585.
Change the YAML version to '2.0' and save the file.
Check both Microcks instances. Version 2.0 appears on http://localhost:8586, although the command explicitly selected the configuration pointing to port 8585
Activity
Syedowais312 commentedon Nov 13, 2026
CC @Harsh4902 @Caesarsage
The fix would be to save the selected --config path in the watch entry and reuse it for subsequent imports instead of loading the default config.
If you confirm this bug and the approach looks good, I can open a PR with the fix.