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.

Sign up for GitHub

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

Jump to bottom

regression starting in 0.5.0 #75

Closed
aaronhmiller opened this issue Sep 12, 2019 · 0 comments
Closed

regression starting in 0.5.0 #75

aaronhmiller opened this issue Sep 12, 2019 · 0 comments

Comments

@aaronhmiller
Copy link

aaronhmiller commented Sep 12, 2019 •
edited
Loading 

# deck version
decK v0.5.1 (5a46dad) 
# deck dump
Error: reading configuration from Kong: looking up consumer 'e2eef88d-ea01-44f1-a045-8dd6dfbf1ec3' for key-auth '64fc16c0-6122-4bd3-80ad-542183bee29c': entity not found```

however, w/o change to Kong:
# curl -sL https://github.com/hbagdi/deck/releases/download/v0.4.0/deck_0.4.0_linux_amd64.tar.g
z -o deck.tar.gz
# tar -xf deck.tar.gz -C /tmp
# cp /tmp/deck /usr/local/bin/
# deck version
decK v0.4.0 (71b7389) 
# deck dump
#
@hbagdi hbagdi closed this as completed in da787d7 Sep 16, 2019
rainest pushed a commit that referenced this issue Apr 21, 2021
@hbagdi
fix(dump) skip Developer Portal credentials in Kong Enterprise
aa49059 
Kong Enterprise Developer Portal exposes the credentials (basic/key) of
Developers on the Admin API, but doesn't expose the consumers causing
issues during export.

The root cause here is in Kong Enterprise but to help out decK users,
I'm going to put a work-around into decK.

The fix here is that for any basic and key auth credential, if the
associated consumer is not found by decK, it will not be exported.

Fix #75
AntoineJac pushed a commit that referenced this issue Jan 23, 2024
@hbagdi
fix(dump) skip Developer Portal credentials in Kong Enterprise
35b8f29 
Kong Enterprise Developer Portal exposes the credentials (basic/key) of
Developers on the Admin API, but doesn't expose the consumers causing
issues during export.

The root cause here is in Kong Enterprise but to help out decK users,
I'm going to put a work-around into decK.

The fix here is that for any basic and key auth credential, if the
associated consumer is not found by decK, it will not be exported.

Fix #75
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aaronhmiller