Skip to content

fix: remove invalid 'gb/txl' from InMemoryDB location list - #704

Closed
dhermann-ionos wants to merge 1 commit into
masterfrom
fix/imdb-gb-txl-location
Closed

dhermann-ionos wants to merge 1 commit into
masterfrom
fix/imdb-gb-txl-location

Conversation

@dhermann-ionos

@dhermann-ionos dhermann-ionos commented Aug 19, 2026 •

Copy link
Copy Markdown

Summary

  • InMemoryDBLocations in internal/constants/constants.go included "gb/txl", which isn't a real IONOS location — txl is a de location (already listed as de/txl), and gb only has lhr/bhx.
  • This made unscoped list commands (e.g. ionosctl dbaas inmemorydb replicaset list) issue an extra request to the non-existent in-memory-db.gb-txl.ionos.com endpoint.

'txl' is a de (Berlin) location, already correctly listed as
de/txl. gb only has lhr/bhx. The bogus entry caused unscoped
'ionosctl dbaas inmemorydb replicaset list' to fan out a request
to a non-existent in-memory-db.gb-txl.ionos.com endpoint.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@avirtopeanu-ionos

Copy link
Copy Markdown
Contributor

Hi! Thanks for opening this PR! Unfortunately we have already fixed this on master, fixed by #691, and you can confirm by checking the master's up to date state.

You can also verify by solving the conflicts on this PR and then the diff will collapse to empty, because that is the state of the master branch.

In any case, thank you for double checking and finding this bug! We are aware that the latest CLI version v6.10.3 has this bug and we are working on releasing the fixed v6.10.4 version!

@dhermann-ionos

Copy link
Copy Markdown
Author

Thank you!

@dhermann-ionos
dhermann-ionos deleted the fix/imdb-gb-txl-location branch September 16, 2026 09:13
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.

2 participants