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.
Test mode (aka "dry run")
See original GitHub issueWe may want to consider a feature where you can run import but in test mode, so no changes. This would be useful for when deploying to production.
It should be fairly easy to add --test param.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:59
- Comments:14 (2 by maintainers)
Top Results From Across the Web
Dry Run Your Test - TestNG Docs
When launched in dry run mode, TestNG will display a list of the test methods that ... You can enable dry run mode...
Read more >Ansible Dry Run - How to Run Playbook in Ansible Check mode
Ansible Dry Run or Ansible Check mode feature is to validate your playbook before execution. With the Ansible Dry Run feature, ...
Read more >APIServer dry-run and kubectl diff - Kubernetes
The existing solution is to run kubectl apply --dry-run , but this runs a local dry-run that doesn't talk to the server: it...
Read more >Dry Run or test mode - Acrosync
Hi, I am testing Acrosync for windows and it do the job, can sync easily 200000+ files for about 300Go of data.
Read more >How To Dry Run Or Simulate Linux Commands - OSTechNix
Simulation is being used in many fields for teaching, testing, training purposes and solving problems. Now let us get back and learn how...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This would be very useful in CI!
With respect to the naming:
--testis fine, however I think--dry-runwould be more clear.Little update on the Auth0 side – we’ve identified this as a high-impact feature and have it prioritized fairly high on the roadmap. Compared to some of the other initiatives we’re working on, this skews towards the larger side and it’s something we want to get right, so we’re taking our time. However, we do see ourselves working this fairly soon!
I’d also like to take a moment to plug Auth0’s Terraform Provider which provides this as a first-class feature already. If you already support Terraform workflows, you may find it to be more suitable to your needs. Both tools with exist alongside each other well into the future.