Skip to main content

Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.

4449 Ideas

amitgadhavi
Participant
amitgadhaviParticipant

Make FME Flow Version Control Work for Modern Git PracticesOpen

FME FLOW Version Control could become an awesome feature for FME but currently it has some basic issues that urgently need to be addressed.  Few of our biggest challenges are, The ability to establish integration with GIT via FME Flow should be straightforward. Currently we are struggling with even this basic connectivity. The basic Fetch and Push to GIT features are not working. Not even one example works even though manual Command line GIT Connectivity is successful from our end. a. Detailed documentation on FME Flow-GIT hub connectivity with videos/examples along with troubleshooting and whitelisting on Networking including Zscaler should be available. b. Main branch has to be renamed to Master. Such hardcoding should be removed and process should be more flexible.       2. Inability to create branching or work with branches via Version Control. Can only connect to           Main branch. Multiple branches cannot connect or integrate.          CI/CD cannot be completed without this. How will developers promote and get           reviewed on their individual work without this feature? Note - Ideally FME Flow Version Control is more preferred than REST API as Version Control is an integral part of FME Flow and users like to use this integral feature more often than others. FME should try to focus and enhance this integral/inbuilt feature over other difficult time-consuming solutions.