You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose that initially the debug report contains:
A tree from "project_path"
A DiGraph representation of dependencies
Full print out of StackGraph (containing generated stacks)
The output from validate() on each template.
We could potentially add to this:
some fuzzy searches against a bunch of v1->v2 checks. I.e. we could highlight where keywords from v1 still exist such as environment, environment_path, environment_config.
some fuzzy searching for potentially misspelt known config keys.
We would need to be aware of making sure users don't inadvertently share secrets.
The text was updated successfully, but these errors were encountered:
Proposal
Add a convenience CLI command and API method that would generate useful information for users to share when raising issues.
Much of the time the same questions are asked when helping users to debug issues. This includes:
Structure of the command/api would be something like
I propose that initially the debug report contains:
tree
from "project_path"validate()
on each template.We could potentially add to this:
some fuzzy searches against a bunch of v1->v2 checks. I.e. we could highlight where keywords from v1 still exist such as
environment
,environment_path
,environment_config
.some fuzzy searching for potentially misspelt known config keys.
We would need to be aware of making sure users don't inadvertently share secrets.
The text was updated successfully, but these errors were encountered: