Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] containerless-kantra: kantra transform rules is by default running in containers #392

Open
1 task done
kthatipally opened this issue Nov 26, 2024 · 1 comment
Open
1 task done
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@kthatipally
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

v0.6.0-beta.1

Priority

Major

Current Behavior

I am attempting to use the transform command to convert Windup XML rules to YAML format. However, I observe that the shim utility automatically runs within the containers by default.

.\windows-kantra.exe transform rules --input .\transform\ --output .\transform-yaml

Could you please add container-less support to the transform command. Let me know if you need any additional details

Expected Behavior

Transform rules should be able to run in the container less-mode respecting -run-local setting

How Reproducible

Always (Default)

Steps To Reproduce

  1. OS: Windows
  2. Run .\windows-kantra.exe transform rules --input .\transform\ --output .\transform-yaml
  3. runs in containers by default.

Environment

- OS: win

Anything else?

No response

@kthatipally kthatipally added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 26, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant