[FEATURE REQUEST] States for running sql scripts #67592
OrangeDog
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
Needing to manage an SQL database beyond what is currently provided by db/schema/user/group states. In particular the creation and updating of tables/views/sequences/triggers/constraints/rows. Or running SQL scripts provided by applications that is needed to initialise them.
Describe the solution you'd like
Something like an
sql.applied
state, ideally backend-independent but I don't think that's feasible given how the current db connections are designed (i.e. they run the backend's CLI tool instead of using a PEP 245 API).Describe alternatives you've considered
A suite of
table.present
/absent
,column.present
/absent
,view.present
/absent
, etc. states for every backend could be implemented. It would be more Salty and easier to be stateful, but would also be considerably more work.Implementing a custom module: https://gist.github.com/OrangeDog/49871e06b017318b7498b810e2ad7caa
Additional context
This is a duplicate of #4697
Please Note
If this feature request would be considered a substantial change or addition, this should go through a SEP process here https://github.com/saltstack/salt-enhancement-proposals, instead of a feature request.
Beta Was this translation helpful? Give feedback.
All reactions