You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.
This might be user error. I'm looking at the second example and the string interpolation and there's a value there for ${database} but that's not a field in a standard SQL user secret. I created a metadata field named database and added my value there but it didn't like it.
Am I missing something or is this a problem with the documentation? SQL accounts live at the server level so specifying database seems like something that might not work.
The text was updated successfully, but these errors were encountered:
These fields are straight from the secret template rather than the metadata. You should be able to edit your SQL server template and add any field you desire.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This might be user error. I'm looking at the second example and the string interpolation and there's a value there for
${database}
but that's not a field in a standard SQL user secret. I created a metadata field named database and added my value there but it didn't like it.Am I missing something or is this a problem with the documentation? SQL accounts live at the server level so specifying database seems like something that might not work.
The text was updated successfully, but these errors were encountered: