SKIP_EMAIL_VERIFICATION_IN_DEV Usage in Pipeline
I am working on creating a pipeline to run some e2e-tests where I set the
SKIP_EMAIL_VERIFICATION_IN_DEV variable to true. When I run the tests locally, this variable behaves as expected where the set user doesn't need to verify their email. When I run the same tests within a bitbucket pipeline the tests are getting snagged on logging in requiring verification despite the variable being set.
After reviewing the docs I see that there is specific mention of "development mode" for the usage of this variable so i'm curious if there's more to that definition? Has anyone else ran into this or has any ideas on how to get this variable to behave as expected in a bitbucket pipeline?3 Replies
Hi @Bri. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I can offer some insights into your question about the
SKIP_EMAIL_VERIFICATION_IN_DEV variable and its behavior in different environments.
The SKIP_EMAIL_VERIFICATION_IN_DEV variable is indeed designed for use in development mode, as mentioned in the Wasp documentation on email verification flow (https://wasp-lang.dev/docs/auth/email#email-verification-flow). The documentation states:
This feature is specifically intended for development purposes, to make it easier to test and develop your app without going through the email verification process each time.
The fact that it works locally but not in your Bitbucket pipeline suggests that the pipeline environment might not be recognized as a development environment by Wasp. Unfortunately, the provided knowledge sources don't contain specific information about how Wasp determines whether it's running in development mode or how to configure this for CI/CD pipelines.
To address your issue, you might want to consider the following approaches:
1. Check if there's a way to explicitly set the environment to development mode in your Bitbucket pipeline configuration.
2. Look for any environment variables or configuration settings in Wasp that determine the running mode (development vs. production) and ensure these are set correctly in your pipeline.
3. As an alternative for testing purposes, you might want to explore using the Dummy email provider for development and testing, as mentioned in the Wasp documentation on email providers (https://wasp-lang.dev/docs/advanced/email#using-the-dummy-provider). This could potentially bypass email verification issues in your test environment.
If these approaches don't resolve the issue, you may need to reach out to the Wasp community or maintainers for more specific guidance on how to handle email verification in CI/CD pipelines. The provided knowledge sources don't contain enough information to give a definitive solution to your specific pipeline scenario.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Bri, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@Vinny (@Wasp) you used this successfully in the e2e tests in Github Actions?
Hi, this is resolved, there was a typo on my end when passing in the value via the repository variables. This works as expected. Thank you