-
Notifications
You must be signed in to change notification settings - Fork 415
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
fix: don't create feature export before launch darkly import #3510
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
This change seems to have correctly removed the broken request to |
@matthewelwell, I added a fix for a race condition that could have been triggering the issue, could you please review it? |
@novakzaballa can you provide more information about the change that you made, I don't quite understand it. |
Slack thread on the above topic here. |
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Fixes #3509
Note that it does not make much sense to run an export prior to an LD import since the import is only really useful for new projects. The feature export (I believe) was being done to create a sort of back up but it was not providing the environment id (because there is no contextual environment here).
How did you test this code?
Tested using the production preview but I'm still not seeing the correct behaviour. See comment here.