bug? import database, asset type error and missing name?

[byte-opps]

An example of asset file for a mssql data base table using

$bruin import database -c mssqldb pipe3

missing name: and incorrect type: ?

type: sf.source  --> believe this is SnowFlake?
description: Imported table schema.table

expected result using https://getbruin.com/docs/bruin/commands/import.html

type: postgres  # or snowflake, bigquery, etc.  --> quessing this should be ms.sql or ms.source 
name: schema.table
description: "Imported table schema.table"

 bruin --version
Current: v0.11.352 (c346a9dadbc5f9d69321bdfd046fd9380ea2c77f)
Latest: v0.11.352

[byte-opps]

so studying the manual again, and having updated to the latest version, which includes #1324 which does indeed fix the columns definitions from mssql source. running bruin import I see that the assets are created as /asset/<sql schema name>/<sql table name>.asset.yml with the above issues? but also should it not be of a type name ending in ...asset.sql like page https://getbruin.com/docs/bruin/assets/sql.html ? with /# bruin tags and a default select <all columns names, ...> from <schema.tablename> default template, maybe that template could be user defined?

[karakanb]

the SQL assets do not require .asset.sql in the end, it is sufficient that they end with .sql. Could you please expand a bit more on what are the issues that are still pending?

[byte-opps]

When using bruin import database on a mssql database the asset.yml is created with a type of type: sf.source which I don't think is correct? I would have expected type: ms.sql ?

[karakanb]

@byte-opps just a quick note: it seems like there were some gaps in our docs for this, we have improved the docs and fixed the type as well, wanted to keep you posted.