Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add sceptre debug command #553

Closed
ngfgrant opened this issue Dec 11, 2018 · 3 comments
Closed

Add sceptre debug command #553

ngfgrant opened this issue Dec 11, 2018 · 3 comments

Comments

@ngfgrant
Copy link
Contributor

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:

  • project structure
  • output of config files
  • dependencies output

Structure of the command/api would be something like

sceptre debug OUTPUT_PATH
context = SceptreContext(project_path, command_path)
plan = SceptrePlan(context)
plan.debug("path/to/save/report)

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.

@1oglop1
Copy link
Contributor

1oglop1 commented Dec 26, 2018

I'm on this one.

how do you like folder tree better?

project-dir/ 
     file
     file

    config/ 
         config.yaml

        lab/ 
             config.yaml
             vpc.yaml

or without spaces

project-dir/ 
     file
     file
    config/ 
         config.yaml
        lab/ 
             config.yaml
             vpc.yaml

@ngfgrant
Copy link
Contributor Author

ngfgrant commented Jan 8, 2019

Without spaces please.

@zaro0508
Copy link
Contributor

This issue is old and it hasn't been a huge problem so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants