-
Notifications
You must be signed in to change notification settings - Fork 24
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
ENDOC-588 7.1 update bundle filtering #599
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,11 @@ | ||
# How to customize bundle info shown in Entando App Builder | ||
# Customize Bundle Info Shown in App Builder | ||
|
||
An example of how a bundle is displayed in the Local Hub of the App Builder is shown below: | ||
|
||
 | ||
|
||
In the image above you can see an example of a bundle as is displayed in the Hub user interface inside the Entando App Builder. | ||
|
||
The corresponding custom-resource file on Kubernetes is similar to this: | ||
The corresponding custom resource file on Kubernetes contains content similar to the following: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is minor but should this be "on Kubernetes" or "in kubernetes"? Does a CR file live/act in or on Kubernetes, this always kind of sits odd with me in different contexts There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i think it's "on"... kubernetes runs things on a cluster of hosts... i also think the concept of layering applies, where things are on layers, not in them. pretty sure "in kubernetes" refers to conceptual architecture and "on kubernetes" refers to implementation |
||
|
||
``` | ||
apiVersion: entando.org/v1 | ||
|
@@ -14,7 +15,7 @@ metadata: | |
spec: | ||
details: | ||
name: "Entando Bundle" | ||
description: An example of an Entando bundle | ||
description: An example of an Entando Bundle | ||
dist-tags: | ||
latest: v0.0.1 | ||
time: | ||
|
@@ -32,11 +33,11 @@ spec: | |
# .... | ||
``` | ||
|
||
In order to change the UI elements, you need to update the custom-resource in accordance with this table: | ||
To change the UI elements, update the custom resource in accordance with this table: | ||
|
||
| Field | UI Element | | ||
|---------------------------------|---------------------------------------------------------------------------| | ||
| `spec.details.name` | Set the bundle title | | ||
| `spec.details.description` | Set the bundle description (only visible in the list presentation format) | | ||
| `spec.details.description` | Set the bundle description (only visible in list format) | | ||
| `spec.details.thumbnail` | Set the bundle thumbnail, expressed as a base64 encoded string | | ||
| `spec.details.dist-tags.latest` | Set what's the latest version of the bundle | | ||
| `spec.details.dist-tags.latest` | Set the latest version of the bundle | |
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.
k8s >> K8s
since K8s requires both key and value, are the last two sentences saying you can use anything for value, including true or what?
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.
entando doesn't evaluate value but an entry is required by kubernetes and "true" is recommended