Skip to content
This repository was archived by the owner on Aug 12, 2022. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: cloudquery/cq-provider-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.12.1
Choose a base ref
...
head repository: cloudquery/cq-provider-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.12.2
Choose a head ref
  • 5 commits
  • 7 files changed
  • 4 contributors

Commits on Jun 21, 2022

  1. Configuration menu
    Copy the full SHA
    9dff8a9 View commit details
    Browse the repository at this point in the history

Commits on Jun 22, 2022

  1. chore: Synced file(s) with cloudquery/.github (#368)

    Synced local file(s) with [cloudquery/.github](https://github.com/cloudquery/.github).
    
    
    
    
    
    ---
    
    This PR was created automatically by the [repo-file-sync-action](https://github.com/BetaHuhn/repo-file-sync-action) workflow run [#2540965963](https://github.com/cloudquery/.github/actions/runs/2540965963)
    cq-bot authored Jun 22, 2022
    Configuration menu
    Copy the full SHA
    3310e26 View commit details
    Browse the repository at this point in the history

Commits on Jun 23, 2022

  1. refactor: Use range with values in fromErr (#369)

    * ignore vendor
    
    * simplify fromError a bit
    candiduslynx authored Jun 23, 2022
    Configuration menu
    Copy the full SHA
    6f51f6c View commit details
    Browse the repository at this point in the history

Commits on Jun 24, 2022

  1. fix: Issues when PG username is 'cloudquery' (#371)

    Before this fix, cloudquery misbehaved when the PG username was named 'cloudquery'.
    It created tables in the 'cloudquery' schema instead of the 'public' schema.
    This happened because the search path was  '"$user", public', which means it depended on the username.
    
    This fix, upon connection to PG, will change serach_path to 'public' only, i.e. not dependent on username (which is way more predictable).
    
    This won't impact us explicitly accessing the 'cloudquery' schema via 'cloudquery.<table-name>', which is what we do when we actually need the 'cloudquery' schema.
    shimonp21 authored Jun 24, 2022
    Configuration menu
    Copy the full SHA
    3317cae View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    277946c View commit details
    Browse the repository at this point in the history
Loading