INSTALL onelake FROM community;
LOAD onelake;

-- First, create a secret to authenticate with OneLake.
-- You can use either a service principal or the credential chain (e.g., Azure CLI).
-- Uncomment the desired method and provide the necessary credentials.
set azure_transport_option_type = 'curl';
CREATE SECRET  (
    TYPE azure,
    PROVIDER service_principal,
    TENANT_ID '<your_tenant_id>',
    CLIENT_ID '<your_client_id>',
    CLIENT_SECRET '<your_client_secret>'
);
-- CREATE SECRET  (
--     TYPE azure,
--     PROVIDER credential_chain,
--     CHAIN 'cli'
-- );

CREATE SECRET onelake (
    TYPE ONELAKE,
    TENANT_ID '<your_tenant_id>',
    CLIENT_ID '<your_client_id>',
    CLIENT_SECRET '<your_client_secret>'
);

-- CREATE SECRET  onelake(
--     TYPE ONELAKE,
--     PROVIDER credential_chain,
--     CHAIN 'cli'
-- );

-- Optional: use preissued tokens stored in env variables (defaults shown), if they are already available with the same name, no need to set them here (only update the SET commands if the names are different
--SET onelake_env_fabric_token_variable = 'FABRIC_API_TOKEN';
--SET onelake_env_storage_token_variable = 'AZURE_STORAGE_TOKEN';
--CREATE SECRET onelake_env (
--    TYPE ONELAKE,
--    PROVIDER credential_chain,
--    CHAIN 'env'
--);
-- Combine chain steps if you want CLI fallback
--CREATE SECRET onelake_env_chain (
--    TYPE ONELAKE,
--    PROVIDER credential_chain,
--    CHAIN 'cli, env'
--);

-- Optionally keep the token in-session instead of touching the shell
--SET VARIABLE AZURE_STORAGE_TOKEN = '<preissued_onelake_access_token>';

-- Attach to your OneLake workspace and lakehouse
ATTACH '<your_workspace_name>/<your_lakehouse_name>.Lakehouse'
    AS <your_connection_name>
    (TYPE ONELAKE);

USE <your_connection_name>.<your_schema_name>; -- e.g., dbo

SHOW TABLES;

SELECT * FROM <your_table_name> LIMIT 10 ; -- USING ICEBERG;