Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion spring-platform/FROM-DEMO-TO-PRODUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,8 @@ cub-gen springboot set-embedded-config \
--configmap my-service-config \
feature.myservice.reservationMode optimistic

# Step 5: Initiative GUI proof
# Step 5: Initiative GUI proof, from the cub-gen repo root
cd /path/to/cub-gen
./examples/springboot-paas/demo-initiative-gui.sh
jq '.scenarios[] | {title, changed_field, route, decision, source_file, next_actions}' \
.tmp/springboot-initiative-gui/initiative-card.json
Expand Down
8 changes: 5 additions & 3 deletions spring-platform/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,9 +125,11 @@ jq '.scenarios[] | {title, changed_field, route, decision, source_file, next_act
```

The expected decisions are `ALLOW` for the feature flag, `ESCALATE` for Redis
caching, and `BLOCK` for the datasource override. The Redis case should name
`pom.xml` and `src/main/resources/application.yaml` as the source files to
change or link through a PR.
caching, and `BLOCK` for the datasource override. In the Redis case,
`source_file` should be `src/main/resources/application.yaml`, and
`next_actions[].files` should list both `pom.xml` and
`src/main/resources/application.yaml` as the files to change or link through a
PR.

If you have studied the model here and want to move to real tooling, that is
the bridge.
Expand Down