Fetch DET config files #123
Merged
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.
🦖 SAAS-18883
This change automatically fetches DET config files from CommCare HQ using its DET Export Instance API, instead of requiring the user to download the config file from HQ and then upload it to CommCare Data Pipeline (CommCare Sync).
The approach uses AJAX to get the available form and case exports from HQ to allow the user to select one, and then once the form is submitted, it fetches the config file.
See PR dimagi/commcare-hq#37223 for the DET Export Instance API.
Note
I have used VanillaJS ™ for this change. In the future CommCare Data Pipeline will use HTMX + Alpine, but that is out of scope at the moment.