It looks like the external tables are not "tracked" when running Delta Kusto, therefore we cannot automatically create these tables in the higher environment whenever we have to promote from dev.
In https://github.com/microsoft/delta-kusto/issues/60, you said this was out of scope because of the secret credentials.
Currently, the external tables and continuous export can be used with managed identity, therefore the "secret credentials" problem should not be a blocker anymore.
Is there a way to have this implemented for External Tables?
Also, how about Materialized Views? These also seem to not be detected by the Delta Kusto.
Thanks in advance!
It looks like the external tables are not "tracked" when running Delta Kusto, therefore we cannot automatically create these tables in the higher environment whenever we have to promote from dev. In https://github.com/microsoft/delta-kusto/issues/60, you said this was out of scope because of the secret credentials. Currently, the external tables and continuous export can be used with managed identity, therefore the "secret credentials" problem should not be a blocker anymore.
Is there a way to have this implemented for External Tables? Also, how about Materialized Views? These also seem to not be detected by the Delta Kusto. Thanks in advance!