Skip to content

Conversation

@savme
Copy link

@savme savme commented Nov 9, 2025

What kind of change does this PR introduce?

Dependency update

What is the new behavior?

Latest API client is used.

Additional context

This PR needs #234 to build. Will rebase onto main after it gets merged.

Please ignore golangci-related changes.

dependabot bot and others added 3 commits May 5, 2025 07:48
Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 6 to 8.
- [Release notes](https://github.com/golangci/golangci-lint-action/releases)
- [Commits](golangci/golangci-lint-action@v6...v8)

---
updated-dependencies:
- dependency-name: golangci/golangci-lint-action
  dependency-version: '8'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
OrganizationId: data.OrganizationId.ValueString(),
Name: data.Name.ValueString(),
DbPass: data.DatabasePassword.ValueString(),
Region: api.V1CreateProjectBodyDtoRegion(data.Region.ValueString()),
Copy link
Author

Choose a reason for hiding this comment

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

Region is deprecated in favor of RegionSelection

Comment on lines +439 to +451
if f.CanInterface() {
if v, ok := f.Interface().(interface {
IsNull() bool
IsSpecified() bool
}); ok {
if !v.IsSpecified() {
continue
}

if v.IsNull() {
continue
}
}
Copy link
Author

Choose a reason for hiding this comment

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

Field types changed *T -> nullable.Nullable[T]. This filters null/unspecified fields to match old pointer behavior

ImportStateVerify: true,
ResourceName: "supabase_settings.production",
ImportState: true,
ImportStateCheck: func(is []*terraform.InstanceState) error {
Copy link
Author

Choose a reason for hiding this comment

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

Switched to using ImportStateCheck because marshalling zero-initialized Nullable fields in the mock causes all fields to appear in the response with zero values rather than as null.

This keeps the test focused on the fields explicitly set in the mock for now; happy to revisit if we find a better approach later.

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.

1 participant