Skip to content

CLI reports non-native default config path on Windows #268

Description

@mynk8

Describe the bug

The CLI constructed the ConfigPath variable with mixed seperators and hence, the reported default config path in --help was wrong.

      --config string                 Path to Microcks config (default "C:\\Users\\HomePC/.config/microcks/config")

This seems to be a cosmetic issue only, the actual paths used by the runtime logic is different.

Expected behavior

The expected path should be C:\\Users\\HomePC\\.config\\microcks\\config on Windows

Actual behavior

Reports C:\Users\some_name/.config/microcks/config

How to Reproduce?

Run microcks --help on Windows

Microcks version or git rev

fde7e8f

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

source

Activity

  1. github-actions commented on May 3, 2026

    @github-actions

    👋 @mynk8

    Welcome to the Microcks community! 💖

    Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

    📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

    If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

    Hope you have a great time there!

    🌟 ~~~~~~~~~ 🌟

    📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

    🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

  2. github-actions commented on Jun 3, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity 😴

    It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

    There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

    Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

    Thank you for your patience ❤️

  3. Caesarsage commented on Aug 16, 2026

    @Caesarsage
    Contributor

    Thank you @mynk8

    This should be fixed by #442, which moved config path construction to filepath.Join,the mixed-separator default in --help came from the old path package usage.

    Could you re-verify with a current master build on Windows? If the help output is clean now, this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleState due to inactivity

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions