Is it impossible to release different versions based on staging and production environments?
Currently, I need this functionality for 'module development'. To add and test a module within an app, it has to go through a Public Release. However, when the app developer releases it, the same version gets applied to both the staging and production environments, which makes it difficult to use the app in the production environment.
My ultimate goal is to be able to test in the app's edit mode or in the staging environment before releasing to production.
I don't think this is possible, and I struggle withe the same issue as you when testing mofules. Environments are related to resources, rather than app versions.
@retool team, is there a feature request where you can select which published version of the module to use in an app?? I think this would help a lot!
This is a great shout. To Miguel's point, environments are currently tied to resources and not to apps themselves - of which modules are a subset.
I'll take this request to our dev team to see what can be done! As soon as I have any updates I'll share them here.
Last but not least, I'll just make a note here that you can achieve true differentiation of production and development apps with spaces or with a multi-instance deployment, both of which are available at the Enterprise level.
I did think of a workaround and thought I'd share.
It's definitely not ideal, but you can export the existing module and import the JSON elsewhere for the sake of development. That would at least allow for active embedding and testing without having an affect on production applications.
@Darren@MiguelOrtiz
Thank you both for answering my questions.
I'm having difficulties not only with the initial launch of the app but also with subsequent updates and improvements.
There are so many connected apps, you know
It would be great if there were any updates.
That would at least allow for active embedding and testing without having an affect on production applications.