Create a member list
Author member-list expressions as Python source using the same source registry and embedded editor as other definitions. The application stores the original source and derives its compiled definition on activation.
Example source
In the disposable Operating Data Cube, verify Account members InputA and InputB exist, then use this source with entry point build and an approved environment.
from openepm import MemberListExpression, MemberListVersion
def build(context, parameters):
return MemberListVersion(
"docs.operating-inputs", 1, "Account", "Operating inputs",
MemberListExpression.explicit("InputA", "InputB"),
)Prompt
In {{workspace_id}} / {{application_id}}, verify current rule-design authority and the referenced members.
Save this source as an immutable python.program.save version through execute_v2_python_program_registry, with current metadata/policy/schema pins and one stable save key.
Poll the returned Validation task and correct any source diagnostics. Read the source back and compare sourceDigest.
Test the exact version with python.program.test, parameters {}, definitionParameters {} and current pins. Inspect the returned member-list result and identity without publishing it.
When activation is requested, pass the exact reviewed build ID as validationBuildId to python.program.publish. Verify the derived list's source binding matches the program/version/sourceDigest.
Use metadata.member_list.evaluate for the exact active list version. Reopen its bound Python source for edits; save a new source and definition version.Save and Test do not publish the list. Activation creates the immutable compiled list and its source binding together. Read and evaluation use the existing member-list operations. Direct JSON definition saving is an internal compilation step.