i think we should update all the config_schema arg docstrings to mention this default behavior, e.g. in @solid, SolidDefinition, @resource, and a lot more - esp composite and io manager will behave differently.

as we are updating the logging_tags, can we test it in terminal and dagit to see if the hook events still behave the same

hold until we figure out a plan for the pipeline hook

lg2m. thx!

agreed with removing unnecessary InputDefinitions and OutputDefinitions when introducing inputs and outputs.
but i'd suggest explaining InputDefinition and OutputDefinition more in the explanation sections.

lg2m! thanks for cleaning this up!

the diagnosis looks right to me

add 0.11.3 versioned images

up

clean up testing

not confident about this diff: enabling this test may cause unnecessary trouble for people when the local env isn't set up properly for the docs build.

snapshot and then format

update console.log

up

up

turn on gfm tablePipeAlig

@sashank just to be clear that we are aware of the change, many concept pages will become like this:

landed D7202 which captures broken anchor links and fixed the ones on this page, so please rebase before landing

rebase

• move skipping logic before execute_raw
• update docker tests

execute_raw spins up a docker container so it seems like we need toe execute_raw before raise skipping

some other logic in this operator and the python operator also seem a bit skeptical to me, e.g. we don't pass in solids_to_execute or steps_to_execute to pipeline_run, check_events_for_skips, etc.

up

up