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

Deprecate /api/devfile REST API #13868

Merged
merged 4 commits into from
Jul 22, 2019
Merged

Deprecate /api/devfile REST API #13868

merged 4 commits into from
Jul 22, 2019

Conversation

skabashnyuk
Copy link
Contributor

What does this PR do?

Deprecate /api/devfile REST API

What issues does this PR fix or reference?

need for #13867

Release Notes

n/a

Docs PR

n/a

Signed-off-by: Sergii Kabashniuk <skabashniuk@redhat.com>
@skabashnyuk
Copy link
Contributor Author

ci-test

Copy link
Contributor

@metlos metlos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm generally OK with returning 400 with a meaningful error message but I think we should consider the following:

  • we should remove the swagger docs from the methods
  • what about returning 301 (or maybe even 308) instead?

@che-bot
Copy link
Contributor

che-bot commented Jul 16, 2019

Results of automated E2E tests of Eclipse Che Multiuser on OCP:
Build details
Test report
docker image: eclipseche/che-server:13868
https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

@skabashnyuk
Copy link
Contributor Author

we should remove the swagger docs from the methods

ok

what about returning 301 (or maybe even 308) instead?

My intention was a bit different. It's not just to keep it working it's to identify a place what it used and fix it. I next release we want to remove this api at all because we have analog /api/workspace/devfile.

AFAIK there are no places where we use this api.

@skabashnyuk
Copy link
Contributor Author

@rhopp @nickboldt @sleshchenko @mshaposhnik thoughts?

Copy link
Contributor

@nickboldt nickboldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please tweak the error messages to explain the need for the call to action, and to fix the English syntax.

@skabashnyuk
Copy link
Contributor Author

@nickboldt your comments have been addressed

@skabashnyuk
Copy link
Contributor Author

ci-test

@che-bot
Copy link
Contributor

che-bot commented Jul 18, 2019

Results of automated E2E tests of Eclipse Che Multiuser on OCP:
Build details
Test report
docker image: eclipseche/che-server:13868
https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

@skabashnyuk
Copy link
Contributor Author

@nickboldt are you ok with the current state of pr?
@eclipse/eclipse-che-qa can I ignore results of crw-ci-e2e-happy-path-test ?

@SkorikSergey
Copy link
Contributor

@eclipse/eclipse-che-qa can I ignore results of crw-ci-e2e-happy-path-test ?

Yes, it is test problem(20 sec was not enough for starting Java language server).

@skabashnyuk
Copy link
Contributor Author

@nickboldt ping

Copy link
Contributor

@nickboldt nickboldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@nickboldt
Copy link
Contributor

@skabashnyuk sorry for slow response. You'd do better to ping on MM, slack, IRC, hangouts or anything that doesn't produce email but a notification of unread messages. :)

Email is the thing I do LAST after all the other hailing frequencies are done.

@skabashnyuk skabashnyuk merged commit fe8e649 into master Jul 22, 2019
@skabashnyuk skabashnyuk deleted the che13867 branch July 22, 2019 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants