-
Notifications
You must be signed in to change notification settings - Fork 16
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
[#51] Provide a default Jakarta EE 10 application to build #52
Conversation
* Use https://github.com/jboss-eap-up-and-running/eap8-getting-started as the default Jakarta EE application This fixes jbossas#51 Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
@@ -2,7 +2,7 @@ | |||
|
|||
A Helm chart for building and deploying a [JBoss EAP 8](https://www.redhat.com/en/technologies/jboss-middleware/application-platform) application on OpenShift. | |||
|
|||
## The Helm Chart for EAP 8 Beta is a Technology Preview feature only. | |||
## The Helm Chart for EAP 8 is a Technology Preview feature only. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technology Preview
I thought it is not Technology Preview anymore for EAP8
@@ -149,7 +149,7 @@ If the application image has been built by another mechanism, you can skip the b | |||
| `build.sourceSecret`|Name of the secret containing the credentials to login to Git source reposiory | - | The secret must exist in the same namespace or the chart will fail to install - [OKD documentation](https://docs.okd.io/latest/cicd/builds/creating-build-inputs.html#builds-manually-add-source-clone-secrets_creating-build-inputs) | | |||
| `build.triggers.genericSecret`| Name of the secret containing the WebHookSecretKey for the Generic Webhook | - | The secret must exist in the same namespace or the chart will fail to install - [OKD documentation](https://docs.okd.io/latest/cicd/builds/triggering-builds-build-hooks.html) | | |||
| `build.triggers.githubSecret`| Name of the secret containing the WebHookSecretKey for the GitHub Webhook | - | The secret must exist in the same namespace or the chart will fail to install - [OKD documentation](https://docs.okd.io/latest/cicd/builds/triggering-builds-build-hooks.html) | | |||
| `build.uri` | Git URI that references your git repo | <required> | Be sure to specify this to build the application. | | |||
| `build.uri` | (**required**) Git URI that references your Git repository | https://github.com/jboss-eap-up-and-running/eap8-getting-started | Be sure to specify this to build your own application. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct to call it required
when default is provided when omitted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is required from a schema perspective (
eap-charts/charts/eap8/values.schema.json
Line 34 in 51c29cb
"uri": { |
The default value in values.yaml
installs an example provided by us. In practice, an user must change that uri
to point to their Git repo if they want to deploy their application.
This fixes #51