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.

Container component restriction should be contained to odo dev #7162

Open
Open
Container component restriction should be contained to odo dev#7162
Labels
kind/user-storyAn issue of user-story kindlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.needs-triageIndicates an issue or PR lacks a `triage/*` and requires one.

Description

@michael-valdron
michael-valdron
opened on Dec 7, 2023

/kind user-story

User Story

As a developer, I want to use odo deploy on outerloop devfiles, so that I can deploy my application using devfile k8s resources without needing a container component.

Currently, there is a restriction on all odo commands to require a container component in order to run them. With the existence of outerloop devfiles this restriction should only apply to odo dev, which needs a container component to run the innerloop setup.

Acceptance Criteria

  • Container component should be required when running odo dev
  • Container component should not be required for other odo commands
  • Any documentation or testing tied to these changes should be updated

Links

  • Related Epic (mandatory): N/A

/kind user-story

Activity

  1. github-project-automation
    added this to odo Projecton Dec 7, 2023
  2. openshift-ci
    added
    kind/user-storyAn issue of user-story kind
    on Dec 7, 2023
  3. github-actions
    added
    needs-triageIndicates an issue or PR lacks a `triage/*` and requires one.
    on Dec 7, 2023

  4. github-actions commented on Mar 7, 2024

    @github-actions
    github-actionsBot
    on Mar 7, 2024 – with GitHub Actions
    Contributor

    A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

  5. github-actions
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 7, 2024

  6. rm3l commented on Mar 8, 2024

    @rm3l
    rm3l
    on Mar 8, 2024
    Member

    /remove-lifecycle stale
    /lifecycle frozen

  7. openshift-ci
    added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 8, 2024
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

    kind/user-storyAn issue of user-story kindlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.needs-triageIndicates an issue or PR lacks a `triage/*` and requires one.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions