You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the latest verison, Bytebase seems to default to the new GitOps connector/API.
This seems to be heavily based on Github Actions.
Is support for Gitlab on the horizon? At the end of the day, it seems to be just API calls - but some sort of starting point and reusable CI/CD component would be appreciated.
For now - is there a way to Opt-Out of the new API and keep the old GitOps Flow - while still being on the latest version? Or do we have to stay on the old version of Bytebase.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey there!
Since the latest verison, Bytebase seems to default to the new GitOps connector/API.
This seems to be heavily based on Github Actions.
Is support for Gitlab on the horizon? At the end of the day, it seems to be just API calls - but some sort of starting point and reusable CI/CD component would be appreciated.
For now - is there a way to Opt-Out of the new API and keep the old GitOps Flow - while still being on the latest version? Or do we have to stay on the old version of Bytebase.
Thanks ❤️
Beta Was this translation helpful? Give feedback.
All reactions