b7cbe60d4b
Interactions between resource refreshes and the 'unless' parameter have been
fixed to follow the behaviour of the 'exec' type.
The 'unless' parameter is now always taken into account, whether in ordinary
operation, during a refresh, or when refreshonly is set to true. The resource
will not run the SQL command when the 'unless' clause matches a row.
Previously a refresh on a resource would ignore the 'unless' parameter if set
which could cause a failure re-running a command, such as attempting to create
a role that already exists.
The following examples have been fixed:
* should not run SQL when refreshed and the unless query returns rows
* with refreshonly should not run SQL when the unless query returns no rows
* with refreshonly should not run SQL when refreshed and the unless query
returns rows
This is done by moving the logic for refreshonly and whether to run the SQL
command from the provider into the type, and consolidating it in the
should_run_sql method which is called during 'command' property retrieval
(instead of sync) and during refresh.
|
||
|---|---|---|
| .. | ||
| lib | ||
| nodesets | ||
| server | ||
| client_spec.rb | ||
| common_patterns_spec.rb | ||
| contrib_spec.rb | ||
| postgis_spec.rb | ||
| postgresql_psql_spec.rb | ||
| server_spec.rb | ||
| unsupported_spec.rb | ||
| validate_db_connection_spec.rb | ||