Skip to content
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

Merged
merged 2 commits into from
Mar 11, 2024

Conversation

matthewelwell
Copy link
Contributor

@matthewelwell matthewelwell commented Feb 29, 2024

Thanks for submitting a PR! Please check the boxes below:

  • I have run pre-commit to check linting
  • I have added information to docs/ if required so people know about the feature!
  • I have filled in the "Changes" section below?
  • I have filled in the "How did you test this code" section below?
  • I have used a Conventional Commit title for this Pull Request

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.

Copy link

vercel bot commented Feb 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 1, 2024 5:23pm
flagsmith-frontend-preview ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 1, 2024 5:23pm
flagsmith-frontend-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 1, 2024 5:23pm

@matthewelwell matthewelwell changed the title Don't create feature export before launch darkly import fix: don't create feature export before launch darkly import Feb 29, 2024
@matthewelwell matthewelwell requested review from a team and kyle-ssg and removed request for a team February 29, 2024 16:05
@github-actions github-actions bot added the front-end Issue related to the React Front End Dashboard label Feb 29, 2024
@matthewelwell matthewelwell marked this pull request as ready for review February 29, 2024 16:05
Copy link
Contributor

github-actions bot commented Feb 29, 2024

Uffizzi Preview deployment-47546 was deleted.

@matthewelwell
Copy link
Contributor Author

This change seems to have correctly removed the broken request to create-feature-export but I'm still getting a blank page after confirming the import. @kyle-ssg @novakzaballa might need some further assistance here.

@novakzaballa
Copy link
Contributor

@matthewelwell, I added a fix for a race condition that could have been triggering the issue, could you please review it?

@matthewelwell
Copy link
Contributor Author

@novakzaballa can you provide more information about the change that you made, I don't quite understand it.

@matthewelwell
Copy link
Contributor Author

Slack thread on the above topic here.

@matthewelwell matthewelwell added this pull request to the merge queue Mar 11, 2024
Merged via the queue into main with commit afadf5a Mar 11, 2024
21 checks passed
@matthewelwell matthewelwell deleted the fix/launch-darkly-import branch March 11, 2024 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
front-end Issue related to the React Front End Dashboard
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: Launch Darkly import failing
3 participants