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

fix(state) drop index on target.Target #280

Merged
merged 1 commit into from
Mar 8, 2021
Merged

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented Mar 7, 2021

target.Target represents an IP address or a DNS name in Kong. These can
be same across different Upstreams.
Drop the unique index on Target resource for this reason.

This is similar to the fix applies to ServiceVersion resource in
cf44212.

The test has been updated to remove insertion of Upstream which doesn't
add in value.

Fix #233

target.Target represents an IP address or a DNS name in Kong. These can
be same across different Upstreams.
Drop the unique index on Target resource for this reason.

This is similar to the fix applies to ServiceVersion resource in
cf44212.

The test has been updated to remove insertion of Upstream which doesn't
add in value.

Fix #233
@hbagdi hbagdi requested a review from a team as a code owner March 7, 2021 16:36
@mflendrich mflendrich merged commit a640f10 into main Mar 8, 2021
@mflendrich mflendrich deleted the fix/duplicate-targets branch March 8, 2021 14:55
rainest pushed a commit that referenced this pull request Apr 21, 2021
target.Target represents an IP address or a DNS name in Kong. These can
be same across different Upstreams.
Drop the unique index on Target resource for this reason.

This is similar to the fix applies to ServiceVersion resource in
cf44212.

The test has been updated to remove insertion of Upstream which doesn't
add in value.

Fix #233
AntoineJac pushed a commit that referenced this pull request Jan 23, 2024
target.Target represents an IP address or a DNS name in Kong. These can
be same across different Upstreams.
Drop the unique index on Target resource for this reason.

This is similar to the fix applies to ServiceVersion resource in
512d53f.

The test has been updated to remove insertion of Upstream which doesn't
add in value.

Fix #233
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.

Error: inserting target into state: inserting target ip:port for upstream xxx: entity already exists
2 participants