li$'ddlZddlmZmZddlmZmZmZmZm Z ddl m Z ddl m Z ddlmZddlmZddlmZdd lmZdd lmZmZmZdd lmZdd lmZmZdd lm Z m!Z!dee"fdZ#Gdde"Z$dedee"effdZ%eGdde!Z&eGdde!Z'eGddeZ(eGdde(Z)dZ*eGdde(Z+y)N) dataclassfield)AnyDictListOptionalUnion)Pattern) Annotated)hooks)Docs) ModelHookType)validate_color) BaseConfigCompareBehavior MergeBehavior)OnConfigurationChangeOption)Metadata ShowBehavior)ValidationError dbtClassMixinreturncgSNrf/var/www/html/strategist-ai/venv_dbt/lib/python3.12/site-packages/dbt/artifacts/resources/v1/config.pylist_strrs Irc eZdZy)SeverityN)__name__ __module__ __qualname__rrrr r srr metasc:i}|D]}|j|}|Sr)meta)r$existingms rr$r$s)!H $66(#$ Orc*eZdZUdZeed<dZeed<y)ContractConfigFenforcedT alias_typesN)r!r"r#r+bool__annotations__r,rrrr*r*!sHdKrr*c:eZdZUeed<dZeed<dZee ed<y)HooksqlT transactionNindex) r!r"r#strr.r2r-r3rintrrrr0r0's HKE8C=rr0c>eZdZUdZeed<edejjZ e e ed<edejjZ e e ed<edejjZe e ed<eeeej$ej(ejZeee e fed <eeej2jZ ee efed <edejjZe e ed <y) NodeAndTestConfigTenabledNdefaultmetadataaliasschemadatabasedefault_factoryr;tagsr&group)r!r"r#r8r-r.rrExcluder&r<rr4r=r>rr$rHiderAppendrAr rdictUpdaterrrBrrrr7r7.s-GT! ((--/E8C=" ((--/FHSM$ ((--/Hhsm#( |((-*>*>@W@WX#D%S 3 !%%**,D$sCx.! ((--/E8C=rr7ceZdZUdZeed<dZeeed<dZe ed<dZ e ed<dZ e ed<e e Zeee fed <e eej$d d  Zeeed<e eej$dd  Zeeed<e e ej.j1 Zeee fed<e e ej.j1 Zeee fed<dZeeed<dZeeeedfed<dZeeed<e e jB Z"e ed<e e ejFj1 Z$eee fed<e eej$j1 Z%eeed<e e&ej.j1 Z'e&ed<e e(ej.j1 Z)e(ed<dZ*e ed<dZ+e ed<dZ,e-fdZ.xZ/S) NodeConfigview materializedNincremental_strategy batch_sizelookbackbegin)r@ persist_docsz post-hook)merger<r? post_hookzpre-hookpre_hookquoting column_types full_refresh unique_keyignoreon_schema_changeon_configuration_changegrantspackagesdocscontract event_timeconcurrent_batchesc,|jjr0|jj}t|std|d|jj r8|j dk(r(|jdvrtd|jdyyy)Nz(Invalid color name for docs.node_color: z=. It is neither a valid HTML color name nor a valid HEX code. incremental)append_new_columnsfailz$Invalid value for on_schema_change: zw. Models materialized as incremental with contracts enabled must set on_schema_change to 'append_new_columns' or 'fail')r^ node_colorrrr_r+rKrZ)selfrfs r __post_init__zNodeConfig.__post_init__s 99  --J!*-%>zlKRR MM " "!!]2%%-KK!6t7L7L6MNEE L3 #rct||}tD]0}||vs||Dcgc]}tj|c}||<2|Scc}wr)super__pre_deserialize__rr get_hook_dict)clsdatakeyh __class__s rrkzNodeConfig.__pre_deserialize__sZw*40  HCd{=A#YGU003GS  H HsA )0r!r"r#rKr4r.rLrrMrrOrPrrFrQrlistrrErSrr0rTrGr&rUrVrWr-rXr rZrr:r[ DictKeyAppendr\r]r r^r*r_r`rarh classmethodrk __classcell__rqs@rrIrIMs3L#*.(3-.JHcE3#(#>L$sCx.>!(//+FItDz!(//*EHd4j$%%**,GT#s(^ $)%%**,$L$sCx.$(L(4.'/3Jc49d*+2&.hsm.;@3;;<8#}'B'B'G'G'IFDcN %%**,Hd3i%%**,D$ %&%%**, HnJ""*rrIz)^([Ww][Aa][Rr][Nn]|[Ee][Rr][Rr][Oo][Rr])$cveZdZUdZedej jZe e e d<dZ e e d<e dZee eefe d<d Ze ee d <d Ze e e d <d Ze e e d <d Ze ee d <dZe e d<dZe e d<dZe e d<fdZedee efdee efdefdZefdZ xZ!S) TestConfigFdbt_test__auditr9r=testrKERRORseverityNstore_failuresstore_failures_aswherelimitzcount(*) fail_calcz!= 0warn_iferror_ifct|dddd}dddd}|j||j|_|S|j |jd|_|S)a| The presence of a setting for `store_failures_as` overrides any existing setting for `store_failures`, regardless of level of granularity. If `store_failures_as` is not set, then `store_failures` takes effect. At the time of implementation, `store_failures = True` would always create a table; the user could not configure this. Hence, if `store_failures = True` and `store_failures_as` is not specified, then it should be set to "table" to mimic the existing functionality. A side effect of this overriding functionality is that `store_failures_as="view"` at the project level cannot be turned off at the model level without setting both `store_failures_as` and `store_failures`. The former would cascade down and override `store_failures=False`. The proposal is to include "ephemeral" as a value for `store_failures_as`, which effectively sets `store_failures=False`. The exception handling for this is tricky. If we raise an exception here, the entire run fails at parse time. We would rather well-formed models run successfully, leaving only exceptions to be rerun if necessary. Hence, the exception needs to be raised in the test materialization. In order to do so, we need to make sure that we go down the `store_failures = True` route with the invalid setting for `store_failures_as`. This results in the `.get()` defaulted to `True` below, instead of a normal dictionary lookup as is done in the `if` block. Refer to the test materialization for the exception that is raise as a result of an invalid value. The intention of this block is to behave as if `store_failures_as` is the only setting, but still allow for backwards compatibility for `store_failures`. See https://github.com/dbt-labs/dbt-core/issues/6914 for more information. table ephemeralN)TFNFT)rrrJ)rjfinalize_and_validater~r}get)rgget_store_failures_as_mapget_store_failures_maprqs rrz TestConfig.finalize_and_validates4 %' % !"   ! ! )%>t?R?R%SD " #9"<"  ! rc6|jdrGtjt|jdst d|jddt |||jdr |jddk7r t dyy)Nr|z0Severity must be either 'warn' or 'error'. Got ''rKrzz/A test must have a materialized value of 'test')rrematchSEVERITY_PATTERNrrjvalidate)rmrnrqs rrzTestConfig.validates 88J 1A488JCW(X!B488JCWBXXYZ   88N #(@F(J!"ST T)K #r)"r!r"r#__test__rrrCr&r=rr4r.rKr r|r r rr}r-r~rrr5rrrrrtrrrrrurvs@rrxrxs H"! ((--/FHSML#?G?PHi'*:";;<P%)NHTN)'+x}+E8C=E8C=IsGSHc1ftCH~d38nQU, U Urrx),r dataclassesrrtypingrrrrr mashumaro.jsonschema.annotationsr typing_extensionsr dbtr dbt.artifacts.resources.baser dbt.artifacts.resources.typesrdbt.artifacts.utils.validationr dbt_common.contracts.config.baserrr+dbt_common.contracts.config.materializationr$dbt_common.contracts.config.metadatarrdbt_common.dataclass_schemarrr4rr r$r*r0r7rIrrxrrrrs (334'-79WWSGF$s) s (tCH~ ]    =      < P"P Pf@ gU"gU gUr