libera_utils.aws.constants.ProcessingStepIdentifier

class libera_utils.aws.constants.ProcessingStepIdentifier(value)

Bases: Enum

Enumeration of processing step IDs used in AWS resource naming and processing orchestration

In orchestration code, these are used as “NodeID” values to identify processing steps:

The processing_step_node_id values used in libera_cdk deployment stackbuilder module and the node names in processing_system_dag.json must match these.

They must also be passed to the ecr_upload module called by some libera_cdk integration tests.

__init__(*args, **kwds)

Methods

validate(processing_step)	Validate a processing step string used by the DAG or the orchestration system.
dump([chunk_number])	Convert the ProcessingStepIdentifier to a string suitable for matching with a DAG key or in the processing orchestration system.

Attributes

ecr_name	Get the manually-configured ECR name for this processing step
l2cf
l2_stf
adms
l2_surface_flux
l2_firf
unfilt
spice_azel
spice_jpss
l1b_rad
l1b_cam
l0_jpss_pds
l0_azel_pds
l0_rad_pds
l0_cam_pds
l0_cr
cal_rad
cal_cam

dump(chunk_number: int | None = None) → str

Convert the ProcessingStepIdentifier to a string suitable for matching with a DAG key or in the processing orchestration system.

The chunk_number can be specified when the data product represents a PDS file that is typically provided in 12 2-hour chunks per day. In that case, the chunk_number appears as a suffix to the orchestration step identifier

property ecr_name: str | None

Get the manually-configured ECR name for this processing step

We name our ECRs in CDK because they are one of the few resources that humans will need to interact with on a regular basis.

classmethod validate(processing_step: str) → tuple[ProcessingStepIdentifier, int | None]

Validate a processing step string used by the DAG or the orchestration system.

If successful, returns a tuple containing the ProcessingStepIdentifier and the chunk_number, which can be None if the input string does not contain a valid chunk number.