Hi all

:wave:

Today, @data-mlep has released a new version of RMI, which includes several major and minor improvements from previous release

:yay:

Change logs

Enable KFP for rm-scheduler. From now on, it’s recommended to use KFP to create scheduler instead of using Cloud Composer. To create scheduler using KFP, please refer to this documentation
Re-enable or migrate these serving commands to use KFP:

rmi serving delete
rmi serving set-canary
rmi serving destroy
rmi serving publish-promote command. It’s the best practice to use this command to deploy to prod to ensure deployment in stg == prod

Remove service account creation and role binding via IAC. After some discussion with @data-cde about the purpose of IAC, we decided to re-enable this again to make development flow as smooth as possible. Thus, you don’t need to do these steps via IAC. RMI will automatically do this for you :party_parrot:
Replace data-jenkins-bot with data-github-bot so you don’t need to create another PR to add data-jenkins-bot to your repo and wait for @data-cde to approve the invitation :brown-hooray:

What RMI users need to do

Update your RMI version to v3.1.0 by executing rmi update -v v3.1.0 . Please update the RMI version to v3.1.0 in your local computer and CI/CD pipeline before May 28th so we can start decommissioning data-jenkins-bot soon.

Reference

Support

Got any questions? Feel free to contact @data-mlep via #rm-support slack channel

Thanks!

:bows:

:traveloka: Raring Meerkat CLI v3.1.0 Release :traveloka:

Change logs

What RMI users need to do

Reference

Support