Releases: Titan-Systems/titan
Releases · Titan-Systems/titan
v0.9.1
What's Changed
- Fixes an issue where specifying run mode on the command line didn't work
- Fixes an issue with Warehouses not working on Standard-edition Snowflake accounts
- Fixes an issue with resources being dropped out-of-order in sync mode
- Fixes an issue with drift related to public schemas
- Fixes an issue with the
COMMENT
property rendering to SQL incorrectly - Fixes an issue related to creating Database Roles
- Fixes an issue related to specifying column names without data types for Views
Full Changelog: v0.9.0...v0.9.1
v0.9.0
What's Changed
Breaking Changes
- Titan no longer supports modifications to
PUBLIC
schema. This behavior was previously supported but caused a number of bugs. Changes toPUBLIC
schema are non-standard, even if technically allowed by Snowflake. - Blueprint run_mode
SYNC-ALL
has been deprecated, useSYNC
instead. - User property
user_type
has been renamed totype
(#92) - Table resource now ignores changes to columns by default. This is designed to prevent data loss by default
- Some old deprecated modules have been removed.
New Features
- YAML config now supports the alias "grants_on_all" for
GrantOnAll
resources. (#94) - vars. Titan now supports
vars
in both Python and YAML configs. To use a var with a resource:
titan.yml
vars:
- name: foobar
type: string
default: some_default_value
sensitive: true
databases:
- name: "db_{{ var.foobar }}"
titan plan --config titan.yml --vars '{"foobar": "blimblam"}'
titan plan --config titan.yml --vars 'foobar: blimblam'
Python
from titan.blueprint import Blueprint
from titan import var
# Deferred style
db = Database(name=var.foobar)
# Interpolation style
db = Database(name="db_{{var.foobar}}")
Blueprint(resources=[db], vars={"foobar": "blimblam"})
Bugfixes
- Sync mode not available in CLI (#107)
- Some array props did not render correctly to SQL when the resource was updated (#100)
- User type property does not render to SQL correctly when updating (#92)
- Resources that rely on other resources were not rendering to SQL with the fully qualified name of the other resource (#98)
- Wrong order of keywords on creating transient database (#97)
- Database roles cannot be specified as owners (#96)
Resources
- Iceberg Table (#111). This only supports a single variant, more to come in a later release.
- External Volume
Other
- jinja2 has been added as a dependency. I personally apologize.
Full Changelog: v0.8.9...v0.9.0
v0.8.9
What's Changed
- fix image repo fetch when database doesnt exist by @titan-teej in #93
Full Changelog: v0.8.8...v0.8.9
v0.8.8
What's Changed
- Fix a crash when attempting to
export --all
on a trial account - Fixed an issue when exporting databases and tables where resources of the wrong type were being exported
- Export no longer attempts to export database shares
Full Changelog: v0.8.7...v0.8.8
v0.8.7
What's Changed
- Improved performance of
export
CLI for accounts with many resources, particularly grants
Full Changelog: v0.8.6...v0.8.7
v0.8.6
What's Changed
- Added new resources: Notebook, NetworkPolicy
- Added a new example: UNC5537-account-hardening
- Added support for the new User field
user_type
- Grant will now raise an error if used with the OWNERSHIP priv
- Fixed issues with CSVFileFormat, MaterializedView, GrantOnAll,
- Fixed multiple issues related to databases named
DATABASE
(please dont do this) - Fixed drift issues with tags and resources with column fields
- Improved test coverage for drift-after-apply problems
- Automated some internals around privilege type checking
Thanks to @toadies and @noel for the bug reports!
Full Changelog: v0.8.5...v0.8.6
v0.8.5
v0.8.4
v0.8.3
v0.8.2
What's Changed
- Added
--all
flag to the export CLI command. Usage:titan export --all --exclude=network_rule
- Fixed how resources are specified for the export CLI command
Full Changelog: v0.8.1...v0.8.2