p2p-showcase
Showcase lets you try the application after its build, while the rest of Fast
Feedback continues. It deploys the same version that just passed p2p-build
from the FF registry to a separate showcase namespace on the FF cluster.
It does not wait for integration, rebuild the image or select another version.
The reusable FF workflow accepts showcase, a boolean defaulting to false.
Only flagged runs on the configured main branch deploy it. Supported generated
workflows expose the flag on manual dispatch; push and PR runs leave it off.
The new-app wizard always passes true and displays access in a separate Preview
box between RBAC/environment setup and CD pipeline execution. It offers Open app
once authenticated ingress reports readiness. Disabling application ingress still prevents a browser
link. The deployment remains running; later unflagged runs leave it alone.
Application contract
p2p-showcase: deploy-showcaseThe six web templates provide this target and p2p/config/showcase.yaml.
The usual Helm deployment uses the built application image and Showcase-specific
namespace and ingress values. It runs no integration tests.
Showcase runs alongside functional, NFT and security checks. It is not an integration or promotion dependency, but its failure fails the overall FF run. The wizard then uses ordinary failed-workflow recovery before later dispatches. Opening Showcase does not mean the application has passed the remaining gates.
For managed clusters, compatible Portal and corectl versions must support
corectl p2p targets --showcase. The P2P release must support the flag before a
generated workflow forwards it. Existing repositories are not rewritten.