flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.75k stars 652 forks source link

[BUG] Improve ease of locally running flyteadmin integration tests #518

Open katrogan opened 4 years ago

katrogan commented 4 years ago

Describe the bug In short the current system for running integration tests locally on a user's machine lacks polish. It requires manual config tweaking, port-forwarding, etc. This should be investigated to see if it can be improved.

Expected behavior A clear and concise description of what you expected to happen.

Flyte component

To Reproduce Steps to reproduce the behavior:

  1. ...
  2. ...

Screenshots If applicable, add screenshots to help explain your problem.

Environment Flyte component

Additional context Add any other context about the problem here.

yindia commented 3 years ago

It will be cover with issue https://github.com/flyteorg/flyte/issues/1474

katrogan commented 3 years ago

@evalsocket so actually admin integration tests are a different target than endtoend tests. This issue is to address the fact that config changes eg getDbConfig() vs getLocalDbConfig() must be called based on the environment the tests are run in

EngHabu commented 3 years ago

Triage: Looks like nobody is working on this for the foreseeable future. Will revisit in the next bugSquash sprint.

yindia commented 2 years ago

@EngHabu i did some work in issue https://github.com/flyteorg/flyte/issues/1474.

kumare3 commented 2 years ago

I do not think this is a bug, this is a housekeeping issue. Relabeling

yindia commented 2 years ago

yes

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 1 year ago

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

github-actions[bot] commented 3 months ago

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏