-
Notifications
You must be signed in to change notification settings - Fork 24
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
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/plugin-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.48.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: cloudquery/plugin-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.49.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 13 files changed
- 2 contributors
Commits on Jun 24, 2024
-
chore(deps): Update module github.com/cloudquery/plugin-sdk/v4 to v4.…
…48.0 (#1773) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/cloudquery/plugin-sdk/v4](https://togithub.com/cloudquery/plugin-sdk) | require | minor | `v4.47.1` -> `v4.48.0` | --- ### Release Notes <details> <summary>cloudquery/plugin-sdk (github.com/cloudquery/plugin-sdk/v4)</summary> ### [`v4.48.0`](https://togithub.com/cloudquery/plugin-sdk/releases/tag/v4.48.0) [Compare Source](https://togithub.com/cloudquery/plugin-sdk/compare/v4.47.1...v4.48.0) ##### Features - Enable batching resources on source side by default ([#​1771](https://togithub.com/cloudquery/plugin-sdk/issues/1771)) ([1a99a66](https://togithub.com/cloudquery/plugin-sdk/commit/1a99a66c23cf039e74dac089c8b67d9953653c51)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQxNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWVyZ2UiXX0=-->
1Configuration menu - View commit details
-
Copy full SHA for 063c358 - Browse repository at this point
Copy the full SHA 063c358View commit details -
fix(deps): Update module github.com/hashicorp/go-retryablehttp to v0.…
…7.7 [SECURITY] (#1774) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/hashicorp/go-retryablehttp](https://togithub.com/hashicorp/go-retryablehttp) | indirect | patch | `v0.7.5` -> `v0.7.7` | ### GitHub Vulnerability Alerts #### [CVE-2024-6104](https://nvd.nist.gov/vuln/detail/CVE-2024-6104) go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7. --- ### Release Notes <details> <summary>hashicorp/go-retryablehttp (github.com/hashicorp/go-retryablehttp)</summary> ### [`v0.7.7`](https://togithub.com/hashicorp/go-retryablehttp/compare/v0.7.6...v0.7.7) [Compare Source](https://togithub.com/hashicorp/go-retryablehttp/compare/v0.7.6...v0.7.7) ### [`v0.7.6`](https://togithub.com/hashicorp/go-retryablehttp/compare/v0.7.5...v0.7.6) [Compare Source](https://togithub.com/hashicorp/go-retryablehttp/compare/v0.7.5...v0.7.6) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQxNS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJhdXRvbWVyZ2UiLCJzZWN1cml0eSJdfQ==-->
7Configuration menu - View commit details
-
Copy full SHA for e5e8e7e - Browse repository at this point
Copy the full SHA e5e8e7eView commit details
Commits on Jun 27, 2024
-
feat: Better OTEL traces, add metrics (#1751)
Trying to follow https://www.honeycomb.io/blog/opentelemetry-best-practices-naming to have some convention and namespaces for traces. Also removed `syncDfs` as it doesn't really add additional information. I've added `invocationID` to traces, but not metrics as using a random value for a metric attribute will cause high cardinality (that will increase over time) ---
1Configuration menu - View commit details
-
Copy full SHA for 874c33a - Browse repository at this point
Copy the full SHA 874c33aView commit details -
chore(main): Release v4.49.0 (#1775)
🤖 I have created a release *beep* *boop* --- ## [4.49.0](v4.48.0...v4.49.0) (2024-06-27) ### Features * Better OTEL traces, add metrics ([#1751](#1751)) ([874c33a](874c33a)) ### Bug Fixes * **deps:** Update module github.com/hashicorp/go-retryablehttp to v0.7.7 [SECURITY] ([#1774](#1774)) ([e5e8e7e](e5e8e7e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
1Configuration menu - View commit details
-
Copy full SHA for 7bd5c56 - Browse repository at this point
Copy the full SHA 7bd5c56View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.48.0...v4.49.0