Hiroaki Segawa
Hiroaki Segawa
Current dynein outputs data in JSON format. It is beneficial when you use other tools to extract data because JSON is a well-known format. However, it is problematic if you...
Currently, only the `upd` command provides the sophisticated parser for input, which is implemented by #132. We should offer the same feature for the following commands; - `dy put` -...
Currently, our release process does not create a sha256 file for Windows binary. We need to fix this behavior.
*Issue #, if available:* Implement #199 Sub task of #143 *Description of changes:* This pull request adds integration tests for query command. Additionally, this pull request introduces a separate configuration...
*Issue #, if available:* #143 *Description of changes:* This pull request adds integration tests for scan command. By submitting this pull request, I confirm that you can use, modify, copy,...
Currently, we do not have any GitHub workflow to detect dependency problem. Especially, daily checks is preferable to promptly fix the dependency issue. We should implement the new workflow to...
As I described in [a pull request](https://github.com/awslabs/dynein/pull/205) I created, the developer should use `git-secrets` to prevent the inadvertent committing of credentials into the repository. Besides, it is preferable if we...
We should update the table cache after creating a table and delete the cache after deleting a table. Due to the lack of the above update, dynein raises an unintended...
Currently, the `cargo test` command uses the default configuration directory, `$HOME/.dynein`. This means that our configuration is replaced after `cargo test`. This is not good from the perspective of the...
As discussed in https://github.com/awslabs/dynein/pull/196#discussion_r1531541167, the current retry configuration can be improved to be easily understood and written. The following is the current configuration. ```yaml retry: default: initial_backoff: secs: 0 nanos:...