Skip to content
This repository was archived by the owner on Oct 29, 2023. It is now read-only.

Client detection for imported sandbox doesn't take flavor into account #93

Closed
datacharmer opened this issue Sep 30, 2019 · 1 comment
Closed

Client detection for imported sandbox doesn't take flavor into account #93

datacharmer opened this issue Sep 30, 2019 · 1 comment
Assignees
@datacharmer
Labels
bug

Comments

@datacharmer
Copy link
Owner

When we import a sandbox, dbdeployer tries finding a suitable client by matching the version.
It should, however, take the flavor into account, and avoid a client that has a well matched version but not the same flavor.
@datacharmer datacharmer self-assigned this Sep 30, 2019
datacharmer added a commit that referenced this issue Oct 27, 2019
@datacharmer
Add ability of guessing latest downloads
685b234 
NEW FEATURES
- dbdeployer can guess the next downloadable version with the command
  "dbdeployer downloads get-by-version 8.0 --guess-latest"
  or
  "dbdeployer downloads get-by-version 5.7 --guess-latest"

BUGS FIXED
- Issue #95 mismatched values in fan-in when using nodes > 3
- Issue #93 Client detection for imported sandbox doesn't take flavor into account

TESTING
- Add test for FindOrGuessTarballByVersionFlavorOS
- Add mock test for fan-in nodes
@datacharmer
Copy link
Owner Author

Fixed in release 1.41.0

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

@datacharmer datacharmer

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@datacharmer