Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Housekeeping] Enable verbose logging for sandbox and demo environments

See original GitHub issue

Describe the issue

Currently its hard to debug errors in sandbox and demo environments if the installation fails during helm installation . Enable verbose logging for helm commands and also kubectl commands

https://kubernetes.io/docs/reference/kubectl/cheatsheet/#kubectl-output-verbosity-and-debugging

The default option should be with this flag off.

 flytectl demo start --verbose
 flytectl sandbox start --verbose

Have similar flags during teardown of the environments

flytectl demo teardown --verbose
flytectl sandbox teardown --verbose

What if we do not do this?

Longer debugging cycles

Related component(s)

flytectl,flyte

Are you sure this issue hasn’t been raised already?

Have you read the Code of Conduct?

Issue Analytics

State:
Created a year ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

samhita-allacommented, Oct 6, 2022

@GrayFlash, will have to assign it to Hemanth as he created a PR already.

0reactions

GrayFlashcommented, Oct 7, 2022

Sure working on it @samhita-alla going through the codebase and docs properly.!!

Top Results From Across the Web

Analysis and Recommended Settings of the Security Audit ...

The static settings are stored in table RSAUPROF. The system create table logs for any changes which you can view, i.e using report...

Cisco HyperFlex Systems Troubleshooting Reference Guide, 3.5

Step 5. In each controller VM, search for /var/log/springpath/audit-rest.log. ; Step 6. Open each audit-rest.log file and search for the audit ...

Interactive Web Terminals - GitLab Docs

Interactive web terminals give the user access to a terminal in GitLab for running one-off commands for their CI pipeline. You can think...

@berstend/node-safe - npm

Configure permissions with the command line, environment variables or convenient ... --debug-sandbox Enable verbose debug logging to stdout; --print-sandbox ...

alerta Documentation - Read the Docs

key = demo-key sslverify = off timeout = 10.0 debug = yes. Set environment variables: $ export ALERTA_CONF_FILE=~/.alerta.conf.