Skip to content

fix: Added error when connection configuration is not set#476

Merged
bbernays merged 1 commit into
cloudquery:mainfrom
amanenk:cfg_fix
Apr 1, 2022
Merged

fix: Added error when connection configuration is not set#476
bbernays merged 1 commit into
cloudquery:mainfrom
amanenk:cfg_fix

Conversation

@amanenk
Copy link
Copy Markdown
Contributor

@amanenk amanenk commented Feb 7, 2022

fixes nil pointer exception if connection config is not set

@amanenk amanenk requested review from disq and roneli February 7, 2022 19:13
@github-actions github-actions Bot added the fix label Feb 7, 2022
@disq
Copy link
Copy Markdown
Member

disq commented Feb 7, 2022

When does this happen?

Copy link
Copy Markdown
Member

@disq disq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how this happens, but in general we're against panics, so approving

Copy link
Copy Markdown
Member

@disq disq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

erm, why is cfg.CloudQuery.Connection a pointer, maybe make it a non-ptr value?

@bbernays bbernays merged commit 2674f8e into cloudquery:main Apr 1, 2022
TinLe pushed a commit to TinLe/cloudquery that referenced this pull request Apr 7, 2022
* upstream/main:
  feat: Purge stale data (cloudquery#565)
  feat: Add '--disable-fetch-check' flag (cloudquery#567)
  chore: Sync form .github (cloudquery#569)
  feat: Drift: Improvements (cloudquery#563)
  fix: Added error when connection configuration is not set (cloudquery#476)
  feat: Check for slashes in policy (cloudquery#561)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants