Previously made the Matillion version update from 1.69 to 1.72.7 and all the Bash components got "Deprecated". Currently there is no option to update these Deprecated Components from the UI. We have to drag a new Component of the same type to the canvas and then manually re-enter all the parameters and configuration. This is annoying and time consuming as we have been using widely the component.
They are working fine "as is" but we are planning on making additional version update from 1.72.7 to 1.72.16 so do we have first manually update the components to valid ones or is it safe to do the version update even though the bash components are "Deprecated"?
Any insight on this issue from anyone?
@tuomas.hyssala Even the 1.72.16 update will not change anything on the deprecated components We need to make change of every deprecated components manually only. currently we updated from 1.68.21 to 1.75.8 we faced same issue in many components and some got deprecated especially SENGRID component then I posted it community I got help matillion team they asked me to use the new component instead of deprecated components.
Yep, but we are worrying when the components are already now deprecated when we have the 1.72.7 version so if we would now upgrade to 1.72.16 version so would it stop working or just beeing deprecated? We are using widely the bash component so trying to avoid huge work effort at this point and do the component renewal when we are doing development the interfaces anyhow.
Somehow, in our side we are also having some deprecated bash script still they are working fine, but in future update they will stop work from assumption I don't think any automation upgrade for it .I will make post to matillion about it if any update I will inform you, and our team also have Plan-B to make change to new bash script step by step manually.
Not sure if there is an automated out-of-the-box solution for this one, one thing (which requires some testing of course), is to export the whole project json, find/replace the component ID from the deprecated to the new one and import it back.
And if you are using git within Matillion, import the changed into a 'empty' version and check if the correct orchestration jobs appear in the commit list.
Oh and if you try to just 'import' it all back, import doesn't overwrite, it creates the imported on the side.
Note, the mentioned operation is high risk, do test and double test before just doing.
Hi @tuomas.hyssala I got this message from matillion team
@MichaelBoucht I think it may be too risk.
