Comments (5)
Coincidentally, I think I was the one who raised the issue which eventually lead to the deletion of delete_on_create
, so I'm personally already mostly aware of this change. My request here is more about "a changelog is a good thing to have in general, and on an ongoing basis", rather than any question about this individual breaking change from #15.
Thanks.
from terraform-provider-snowsql.
Thanks for calling this out. I will retroactively update the changelog for releases.
from terraform-provider-snowsql.
#15 should provide some context why the delete_on_create
resource argument was dropped. Specifically these two reasons:
-
#15 allows operators to update the delete snowsql statement when the original statement has a syntax error. It also allows operators to update resources in-place which is consistent with how most providers work.
-
The unconventional function of the
delete_on_create
was causing confusion for some operators.
from terraform-provider-snowsql.
I really like Github Releases to track changes. I just found out there is an auto-generate release notes based of PRs and commit messages. It is pretty slick.
from terraform-provider-snowsql.
from terraform-provider-snowsql.
Related Issues (20)
- Terraform provider changed HOT 5
- No active warehouse selected in the current session HOT 4
- Use list in statement - resource "snowsql_exec" HOT 4
- Warehouse declaration not supported in snowsql provider HOT 6
- Skip revokes HOT 4
- Update resource lifecycle HOT 10
- Error when update block is removed
- feat: Add read lifecycle
- feat: add support for `protocol`and `port` provider argument
- feat: data resource to query snowflake
- bug: `number_of_statements` has no effect on `read` statements HOT 2
- bug: Enters broken state when read statements are bad
- bug: import does not work HOT 2
- feat: `snowsql_exec` name argument should be optional
- bug: `read_results` not json decodable when `read` is not specified
- feat: warn user that update statements are ignored during creation
- bug: The `snowsql_query` data source ID will is always reset even if it has already been set before. HOT 1
- snow_exec gives error on multiple statement HOT 11
- subsequent tf plan and apply dont work HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-snowsql.