Tips and Troubleshooting
With any complex configuration, such as SOLE, things may go wrong from time to time. Don't worry, we have you covered with some handy tips and troubleshooting information.
Your first port of call for this should be our FAQs on our Community site, where you can also ask other questions. Search our documentation for help, including the below topics:
- Implicit or external object deletion
- Deletion prevention of PROD DB and SOLE user
- Resource monitor update
- Revoking privileges on objects shared in multiple environments
We have detailed documentation on each supported object type for specific database objects. Start with Account and browse the other configurable objects using the sidebar menu.
If you don't find the information you need there, let our Support team know.
State reset
One particular issue which may arise from time to time is a loss of sync between your SOLE configuration and Snowflake. Often occurring in development environments where configuration changes come thick and fast, this issue is not usually a big problem, as there's a simple fix: reset the state.
As discussed in previous sections, SOLE uses Terraform to manage some of the interactions with Snowflake, and Terraform uses a state file as part of that process, keeping a record of object configurations between pipeline runs. However, SOLE always scans the Snowflake database before making any changes, so if we have any issues, the state can usually be safely reset
To perform a state reset, simply run your SOLE pipeline in the affected environment with the variable LIFECYCLE_STATE_RESET
set to 1. This will tell SOLE to drop the Terraform state file and rebuild it.
For more information, see the SOLE documentation on state reset.
Debug
If you encounter pipeline errors and the solution is not immediately obvious, rerun the pipeline with the
variable DATAOPS_DEBUG set to 1. Doing so will output additional debug information into the job logs with masked secret values.