Skip to content

fix: added default value for use_legacy_sql field #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

fix: added default value for use_legacy_sql field #426

wants to merge 1 commit into from

Conversation

pawan1210
Copy link
Contributor

  • After upgrading the provider version the resource no longer has any default value for "use_legacy_sql" boolean.
  • Earlier the default value used to be "true". So to retain backward compatibility, the PR makes the field optional by adding the default value as "true".

@pawan1210 pawan1210 closed this Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ayushmjain ayushmjain Awaiting requested review from ayushmjain ayushmjain is a code owner

@bradmiro bradmiro Awaiting requested review from bradmiro bradmiro is a code owner

@davenportjw davenportjw Awaiting requested review from davenportjw davenportjw is a code owner

@q2w q2w Awaiting requested review from q2w q2w is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@pawan1210