Skip to content

[PROD] release PM-6686 - spacetech landingpage - #18

Closed
vas3a wants to merge 6 commits into
masterfrom
PM-6686_prod-release-spacetech-landingpage
Closed

vas3a wants to merge 6 commits into
masterfrom
PM-6686_prod-release-spacetech-landingpage

Conversation

@vas3a

@vas3a vas3a commented Nov 4, 2026

Copy link
Copy Markdown
Collaborator

This pull request introduces support for the SpaceTech challenge form, including its definition, deployment tooling, and notification email flow. It seeds a disabled notification flow for the new form, provides a JSON definition, adds a publication script, and updates documentation and tests to cover these changes.

SpaceTech challenge form and notification flow:

  • Added a new migration (20261102010000_space_tech_challenge_email) to seed a disabled ProcessorFlow for the SpaceTech challenge form, which will email all submissions to a fixed recipient list using environment-supplied settings. This flow is disabled by default and should be enabled after configuration and redeployment. [1] [2]
  • Added a new form definition for the SpaceTech challenge in examples/space-tech-challenge.json.
  • Added a publishing script (scripts/publish-space-tech-challenge.ts) to idempotently register, version, and publish the SpaceTech challenge form to the Forms API, using environment variables for configuration.

Documentation and testing:

  • Updated documentation in docs/data-model.md to describe the new notification flow and its configuration.
  • Added integration test to verify that the SpaceTech challenge email flow is seeded as disabled with settings left to the processor environment.

Policy clarification:

  • Clarified machine identity handling in test/policies.spec.ts by adding tests for the machine identity flag and its effect on actor normalization.

@vas3a
vas3a requested a review from jmgasper November 4, 2026 08:23
@vas3a vas3a closed this Nov 4, 2026
@vas3a
vas3a deleted the PM-6686_prod-release-spacetech-landingpage branch November 4, 2026 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants