-
Notifications
You must be signed in to change notification settings - Fork 427
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.
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
fix: schema_name is optional to enable future pipe grant #1424
fix: schema_name is optional to enable future pipe grant #1424
Conversation
Hello @bennylu2 there is a merge conflict which is a bit confusing for me to decipher since the variables are getting renamed, but the error messages are the same. Can you please rebase to main branch and fix the merge conflict?
|
5a3010f
to
cc4d75d
Compare
@sfc-gh-swinkler rebased and ready for review |
if name, ok := d.GetOk("schema_name"); ok { | ||
schemaName = name.(string) | ||
} else { | ||
schemaName = "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI you don't need to set schemaName to an empty string. Since you already declared it on line 94, and the default value of a type string is an empty string.
@bennylu2 im just going to go ahead an approve this, and fix the issues with go fmt and check docs to get it out in the latest release. For future reference, you need to run |
@sfc-gh-swinkler ah thanks, will keep in mind for future. I thought I did run |
schema_name
optional for future pipe grantsfuturePipes
toonFuture
for consistencyTest Plan
References
#1219