microcks-cli icon indicating copy to clipboard operation
microcks-cli copied to clipboard

Pending Tasks for Microcks CLI

Open karanngi opened this issue 7 months ago • 1 comments

Pending Tasks for Microcks CLI

Testing Strategy

  • [ ] Unit tests at the Go level
  • [ ] Integration tests at the Go level (running Microcks with Testcontainers)
  • [ ] Integration tests at the OS level (issuing commands on the CLI binary)

Documentation

  • [ ] Initialize README with installation notice and basic commands
  • [ ] Complement README or create new markdown files for new features

Packaging

  • [ ] Support apt (Linux/Debian)
  • [ ] Support winget (Windows)

Design Decisions

  • [ ] Decide how to handle complex input (flags, JSON, or file)
  • [ ] Decide how to handle output formats (terminal, JSON, YAML)

Authentication & Context

  • [ ] Implement Login / Logout command
    • [ ] Bypass if local instance is running
    • [ ] Store context and tokens in ~/.microcks
    • [ ] Support OIDC Browser Authentication
    • [ ] Replace client credentials (service account)
    • [ ] List/delete authentication contexts
    • [ ] Associate roles with contexts
  • [ ] Context switching
    • [ ] Allow microcks context set <my-context>

Import Commands

  • [ ] Support import-dir ./my-local-resources
  • [ ] Support import-bundle with Microcks Hub integration
  • [ ] Allow secrets in import-url

Secrets Management

  • [ ] microcks secrets create (with username, password, token, etc.)
  • [ ] microcks secrets list

Service Management

  • [ ] microcks services list
  • [ ] microcks services get <id>

Import Jobs

  • [ ] microcks importjobs create <url> --secret=my-secret

CI/CD & Automation

  • [ ] Update GitHub Actions:
    • [ ] test
    • [ ] import
  • [ ] Update Tekton Tasks:
    • [ ] test
    • [ ] import

// @yada @lbroudoux

karanngi avatar Apr 29 '25 07:04 karanngi

@karanngi We are already keeping track of this at #97.

Harsh4902 avatar Apr 29 '25 08:04 Harsh4902

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

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 :heart:

github-actions[bot] avatar May 30 '25 00:05 github-actions[bot]