Releases: Titan-Systems/titan
Releases · Titan-Systems/titan
v0.11.1
v0.11.0
Titan Core v0.11.0 Release Notes
🐛 Bug Fixes
- Fixed missing database specification for schema resources when exported (#167)
- Addressed privilege order violation for grants on stages (#81)
- Fixed dependency issues where tasks weren't properly respecting their "after" relationships
- Fixed a drift issue with user network policies (thank you @mlavaert)
✨ New Features
- DatabaseRoleGrant: New resource type for managing database role grants (fixes #162, #164, #170)
- MaskingPolicy: Added support for managing Snowflake masking policies (#171)
Full Changelog: v0.10.21...v0.11.0
v0.10.21
What's Changed
- Fixes an issue with improper dependency management upstream caused by
python-snowflake-connector
.
Full Changelog: v0.10.20...v0.10.21
v0.10.20
v0.10.19
v0.10.16
v0.10.13
What's Changed
- [CHORE] test account github workflow by @teej in #146
- [CHORE] test account automation by @teej in #148
- [CHORE] blacksmith.sh: Migrate workflows to Blacksmith by @blacksmith-sh in #149
- [CHORE] tests and docs by @teej in #150
- [BUGFIX] share ownership by @teej in #151
Full Changelog: v0.10.8...v0.10.13
v0.10.8
What's Changed
- [BUGFIX] fix grants on multi word resource types by @teej in #141
- [CHORE] add grant_on_all docstring by @rcohngru-ab-carval in #142
- [BUGFIX]: add synonyms for business critical account edition by @rcohngru in #144
- [BUGFIX] Fix issue with DatabaseRoles not allowed with grants by @teej in #145
New Contributors
Full Changelog: v0.10.4...v0.10.8
v0.10.4
What's Changed
- Fixed an issue where planning would fail to find resources, causing unexpected drift
- Added ScannerPackage resource
- CLI
--config
now accepts a path in addition to a filename --config
option now respects.titanignore
file. This file uses.gitignore
syntax- Tests now run on GCP accounts in addition to AWS
Full Changelog: v0.10.0...v0.10.4
v0.10.0
What's Changed
Breaking changes
- None
New Features
- Added
--allowlist
to CLI commands - Added experimental new feature
for_each
. YAML-defined resources can now be generated dynamically withfor_each
.
-- titan.yml
vars:
- name: schemas
type: list
default:
- schema1
- schema2
roles:
- for_each: var.schemas
name: "AR_{{ each.value }}_ROLE"
titan plan --config titan.yml --vars '{"schemas": ["DEV", "PROD"]}'
- Added experimental new feature
scope
. This allows you to limit a config to a single database or single schema. Some details of this feature may be changed in the future.
One way to use this is to apply a single config to multiple schemas. For example:
-- titan.yml
scope: SCHEMA
database: STATIC_DATABASE
tables:
- name: my_table
columns:
- name: my_column
data_type: string
views:
- name: my_view
as_: SELECT * FROM my_table
requires:
- name: my_table
resource_type: TABLE
titan apply --config titan.yml --schema=DEV_TJ
titan apply --config titan.yml --schema=PROD
Resources
- Added a new resource type:
AccountParameter
- Add export support for Future Grants (#118)
Bugfixes
- Fixed an issue where vars could not be used to name a database (#124)
- Fixed an issue where
apply
CLI would fail if using a pre-defined plan - Fixed an issue where Network Grants could not be synced or exported
Performance Improvements
- Use internal Snowflake API for account type detection instead of the slow SHOW TAGS command (#95)
- Dynamic role selection no longer requires running SHOW GRANTS for every role in session (#122)
New Contributors
Thanks to @dwreeves for contributing comprehensive type checking and @toadies, @nialloriordan, @michael-lemiale, @dsmdavid, @aleenprd, @pikachuev for bug reports!
Special thanks to @littleK0i for helping out with Snowflake system commands.
Full Changelog: v0.9.1...v0.10.0