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

[portal] No error when defining duplicated endpoint's name #436

Closed
vdelattre opened this Issue Feb 8, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@vdelattre

vdelattre commented Feb 8, 2017

Current Behavior

when i define backend, i can define new backend with existing name. No error is shown.
In list, both are shown, but when i open one, it 's always the same is opened.

In document for Expression Language, for endpoints it's written thant endpoint name have to be unique

Your Environment

  • Version used: 1.2.0

@brasseld brasseld added the type: bug label Feb 8, 2017

@brasseld brasseld self-assigned this Feb 8, 2017

@brasseld brasseld changed the title from [Portal] No error on defining backend with existing name to [portal] No error when defining duplicated endpoint's name Feb 16, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 20, 2017

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Feb 20, 2017

hi @vdelattre , this bug will be fixed in the next release.
Do you know how to fix data in your database ?

@NicolasGeraud NicolasGeraud added this to the 1.4.0 milestone Feb 20, 2017

@vdelattre

This comment has been minimized.

vdelattre commented Feb 20, 2017

i renamed endpoint and it solved problem
thanks

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 20, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 20, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 20, 2017

@brasseld

This comment has been minimized.

Member

brasseld commented Feb 21, 2017

@NicolasGeraud, I think you also have to upgrade definition dependency for both gateway and rest-api.

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 21, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 21, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 23, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 23, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-gateway that referenced this issue Feb 23, 2017

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Feb 23, 2017

@brasseld done

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 23, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 27, 2017

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Feb 27, 2017

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 27, 2017

brasseld added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment