Skip to content
This repository was archived by the owner on Apr 1, 2026. It is now read-only.
This repository was archived by the owner on Apr 1, 2026. It is now read-only.

JSON / machine output support for Devfile Components #3521

Closed
#3964
Closed
JSON / machine output support for Devfile Components#3521
#3964
Assignees
girishramnani
Labels
area/devfile-specIssues or PRs related to the Devfile specification and how odo handles and interprets it.estimated-size/S (5-10)Rough sizing for Epics. Less then one sprint of work for one personkind/user-storyAn issue of user-story kindpriority/HighImportant issue; should be worked on before any other issues (except priority/Critical issue(s)).v2Issue or PR that applies to the v2 of odo
@girishramnani

Description

@girishramnani
girishramnani
opened on Jul 8, 2020

/kind user-story

This is a follow up issue for things that the older user story #2835 didn't cover

User Story

As a user I want to list components (openshift or kubernetes ) without creating a component in a directory. Also support for --path flag and json out for devfile v2 components.

Acceptance Criteria

  • It should list components (openshift or kubernetes ) without creating a component in a directory
  • It should support for odo list --path flag
  • Json output for devfile v2 components
  • tests

Criteria for IDEs / implementation

Links

/kind user-story

Metadata

Metadata

Assignees

Labels

area/devfile-specIssues or PRs related to the Devfile specification and how odo handles and interprets it.estimated-size/S (5-10)Rough sizing for Epics. Less then one sprint of work for one personkind/user-storyAn issue of user-story kindpriority/HighImportant issue; should be worked on before any other issues (except priority/Critical issue(s)).v2Issue or PR that applies to the v2 of odo

Type

No type

Projects

odo Project

Status

Done ✅

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    ⚡