cli icon indicating copy to clipboard operation
cli copied to clipboard
verified publisher icon kyma-project

CLI with flag -s "commit" -w "kyma-repo location" wipes eveything from kyma-repo location

Open dbadura opened this issue 3 years ago • 5 comments

Description When you want to deploy kyma from commit, the workspace location is cleaned with ci mode, the workspace directory is wiped. I don't know why the directory is wiped if CLI create directory with commit ID and then put kyma resources into newly created repository

Expected result Kyma CLI shouldn't wipe the whole directory

Actual result Kyma CLI clean all in workspace directory

Steps to reproduce

mkdir /tmp/test
touch /tmp/test/README.md
kyma deploy -s a318bcac41c64c4c5f79465ad257378fed17a945 -w /tmp/test --ci

Troubleshooting

dbadura avatar Feb 02 '22 13:02 dbadura

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

kyma-stale-bot[bot] avatar Apr 03 '22 14:04 kyma-stale-bot[bot]

/remove-lifecycle stale

chrkl avatar Apr 04 '22 13:04 chrkl

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

kyma-stale-bot[bot] avatar Jul 01 '22 10:07 kyma-stale-bot[bot]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten

kyma-stale-bot[bot] avatar Jul 08 '22 11:07 kyma-stale-bot[bot]

This bug totally remove cache in case of different version installation.

dbadura avatar Aug 03 '22 09:08 dbadura

This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

kyma-bot avatar Nov 05 '22 13:11 kyma-bot

This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

kyma-bot avatar Nov 12 '22 13:11 kyma-bot

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

kyma-bot avatar Nov 12 '22 13:11 kyma-bot

Will become obsolete when moving to modularised Kyma.

tobiscr avatar Nov 28 '22 14:11 tobiscr

Closing issue as we are not going to deprecate the command (in favour of modularisation) and not investing further efforts for it

tobiscr avatar Nov 28 '22 15:11 tobiscr