exdx
exdx
Right now the logs at the info level are rather noisy. It's hard to determine what is happening because, for example, authentication logs are emitted at a regular frequency as...
Currently avalanche-ops auto-deletes CloudFormation stacks that failed. But if the command, for example `apply` fails overall, the successful stacks remain on AWS even though the cluster was not created successfully....
Currently in `avalancheup-aws apply` and in various other commands there are places were retries need to be done (for polling the AWS APIs for example). Instead of implementing retries on...
It is difficult to test tools that create extensive amounts of cloud resources during their execution. One possible way is to do the following: * Isolate all calls to the...
Currently avalancheup-aws offers the ability to install a chain after using `apply` to spin up a set of validators. When it comes to deleting the chain however, `delete` only offers...
When using `avalancheup-aws apply` the end result is a list of endpoints and commands that can be run, for things like installing a new chain on the network. These commands...
When running tools like avalancheup-aws frequently, many files get generated: spec files, prometheus rules, etc. These are all by default written to the user's home directory. It may make sense...
As a public project, it would benefit users to have a `CONTRIBUTING.md` doc that explains the nature of the project and how to contribute to it successfully. See https://github.com/operator-framework/rukpak/blob/main/CONTRIBUTING.md for...
It's possible to optimize the Rust CI by caching the cargo home directory, or specifically certain files under `.cargo`, and then sharing those files between different CI jobs. This avoids...
#342 does some QoL linting but there are still some unresolved clippy warnings. Ideal set of steps: * Refactor or `#[allow(...)]` the code to have each warning accounted for *...