sample-accelerators / tanzu-java-web-app

Sample Java Web App

tanzu-java-web-app

NOTE This repo has been archived and the sample has been moved to:
https://github.com/vmware-tanzu/application-accelerator-samples/tree/main/tanzu-java-web-app

This is a sample of a Java Spring app that works with Tilt and the Tanzu Application Platform.

Dependencies

1. kubectl CLI
2. Tilt version >= v0.23.2
3. Tanzu CLI and the apps plugin v0.2.0 which are provided as part of Tanzu Application Platform
4. A cluster with Tanzu Application Platform, and the "Default Supply Chain", plus its dependencies. This supply chains is part of Tanzu Application Platform.

Running the sample

Start the app deployment by running:

tilt up

You can hit the spacebar to open the UI in a browser.

• If you see an "Update error" message like the one below, then just follow the instructions and allow that context:

  Stop! tap-beta2 might be production.
  If you're sure you want to deploy there, add:
      allow_k8s_contexts('tap-beta2')
  to your Tiltfile. Otherwise, switch k8s contexts and restart Tilt.
  

tanzu-java-web-app's Issues

Question: Where can we find the "tanzu" app mentioned within Tilfile ?

Question

Where can we find the tanzu app able to execute the following command tanzu apps workload apply -f ... ?

https://github.com/sample-accelerators/tanzu-java-web-app/blob/main/Tiltfile#L2

Tilt up fails

Running tilt up I get this error:

Traceback (most recent call last):
  /Users/risbergt/workspace/tanzu-apps/my-web-app/Tiltfile:11:9: in <toplevel>
  <builtin>: in k8s_yaml
Error: error converting YAML to JSON: yaml: control characters are not allowed

Add additional common parameters

I'd like to see the following additional options:

iterate-cluster-context: this would be placed in tiltfile for allow_k8s_context vlaue
namespace: this would replace the default namespace in the tiltfile
code-git-repo: replaces sample git repo in the workload.yaml file

VS Code was unable to detect changes to HelloController.java

Using the Tiltfile from the beta-3 branch, my VS Code could not detect changes I made to HelloController.java even though I had AutoBuild set to Enabled. I found when I updated the Tiltfile to include the ant-style wildcard, then the reload occurred as I expected...

['pom.xml', './target/classes'],
live_update = [
sync('./target/classes**/', '/workspace/BOOT-INF/classes')
],

Env post endpoint support requires spring-cloud dependency

Revisiting a bit conversation from yesterday I see that the property with spring-cloud version was removed. That make sense because the spring-cloud dependency isn't there either.

However without spring-cloud dependency these three lines in application.yml don't actually do anything because the support for 'env.post' actuator endpoint is actually not part of core spring boot actuator but is an extension provided by spring-cloud.

  endpoint:
    env:
      post:
        enabled: true

So either we add spring-cloud dependency to the pom. Or we remove the above lines of yaml which don't do anything without it.

I'm not 100% sure what we should do. In the greater scheme of things not having env editing support in app-live-view isn't really big thing so people will hardly notice it isn't there (unless they were specifically trying get to that feature rather than just quickly clicking to trough the ui a bit).