Improve infra as code support#4867
Merged
HenryHengZJ merged 2 commits intoFlowiseAI:mainfrom Jul 21, 2025
Merged
Conversation
HenryHengZJ
approved these changes
Jul 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
This small PR fixes a couple of things that stopped me building some custom infra as code support via the api.
Firstly, you couldn't create document stores with loaders, due to loaders being hard coded
[]. I've changed this to allow it but default to the old behaviour.Secondly when creating credentials via the api, you could not specify the id, leading to a different id in each environment (thus breaking the relationship to vector stores). That commit allows you to use the id (which brings it inline with the create api's for chatflows too which accept id).