Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update where-for-dinner for TP with new DSL and removing TAP/TAS artifacts and instructions #529

Merged
merged 8 commits into from
Sep 26, 2024
Merged
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
20 changes: 0 additions & 20 deletions .github/tests/where-for-dinner-1/assertions.sh
Original file line number Diff line number Diff line change
Expand Up @@ -2,26 +2,6 @@
set -euxo pipefail
pushd $1

# Check that workloads path is rewritten
test -f config/developer/workloads.yaml

# Check that RabbitMQ files exist
test -f config/service-operator/rmqCluster.yaml

# Check that MySQL files don't exist
test ! -f config/service-operator/mysqlInstance.yaml
test ! -f config/app-operator/mysqlResourceClaim.yaml

# Check that cloudevents files don't exist
test ! -f config/app-operator/knEventing.yaml

# Check that security files don't exist
test ! -f config/service-operator/appSSOInstance.yaml

# Check that redis files don't exist
test ! -f config/service-operator/redisInstance.yaml
test ! -f config/app-operator/redisResourceClaim.yaml

./mvnw package

popd
5 changes: 2 additions & 3 deletions where-for-dinner/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,8 @@

The Where for Dinner application can technically be deployed on almost any Cloud Native Buildpack enabled platform. Below are detailed deployment instructions for various platforms:

* [Tanzu Application Platform](doc/TAPDeployment.md)
* [Tanzu Application Services](doc/TASDeployment.md)
* Azure Spring Apps Enterprise (TBD)
* Tanzu Platform for Kubernetes (TBD)
* Tanzu Platform for Cloud Foundry (TBD)

## Description
The Where for Dinner dining search solution is a multi micro-service application that implements a relatively contemporary architecture comprised of the following technologies:
Expand Down
12 changes: 12 additions & 0 deletions where-for-dinner/accelerator.axl
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
engine {

{
Include({'**'})
trisberg marked this conversation as resolved.
Show resolved Hide resolved
+ InvokeFragment("build-wrapper-maven")
}
UniquePath(strategy: UseLast)

// Create the provenance file
Provenance()

}
468 changes: 5 additions & 463 deletions where-for-dinner/accelerator.yaml

Large diffs are not rendered by default.

19 changes: 0 additions & 19 deletions where-for-dinner/catalog/catalog-info.yaml

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

This file was deleted.

12 changes: 0 additions & 12 deletions where-for-dinner/catalog/groups/org.yaml

This file was deleted.

This file was deleted.

This file was deleted.

7 changes: 0 additions & 7 deletions where-for-dinner/catalog/systems/where-for-dinner-system.yaml

This file was deleted.

37 changes: 0 additions & 37 deletions where-for-dinner/doc/DynamicServiceProvisioning.md

This file was deleted.

Loading
Loading