Problem syncing RDS instances because rdsadmin private database · Issue #30 · bytebase/bytebase · GitHub
Skip to content

Problem syncing RDS instances because rdsadmin private database #30

Closed

Description

@lantier

Provide the Bytebase version you are using
0.7.2

Describe the bug

Using PostgreSQL in a AWS RDS managed environment we can't properly sync existent databases because bytebase try to sync with a private database.

image

  1. Create a project
  2. Create a environment
  3. Create a instance ofr existant RDS resource
  4. Try to Sync existant databases

Expected behavior

Import all databases into bytebase without the private ones by RDS, or even if it can't connect with one of the databases the processes import the other accessible ones.

Additional context
In this function we see that bytebase database is excluded from sync, so maybe we can add rdsadmin or cloudsql (for GCP equivalent service) too?

bytebase/plugin/db/pg/pg.go

Lines 327 to 335 in 821a06f

Activity

  1. tianzhou commented on Oct 26, 2021

    @tianzhou
    Member

    @lantier Thanks for providing a detailed bug report. We will work on a fix. FWIW, we used to work on GCP Cloud SQL, and we actually designed that cloudsqlstuff :)

  2. added a commit that references this issue on Nov 8, 2021
    50bf4e6
  3. tianzhou commented on Nov 10, 2021

    @tianzhou
    Member

    The new 0.8.0 release should fix this. Please check the release notes https://github.com/bytebase/bytebase/releases/tag/0.8.0

  4. added a commit that references this issue on Nov 12, 2021
    92d5283
  5. added a commit that references this issue on Nov 19, 2021
    de0c08b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions