-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Prerelease toggle #143853
Prerelease toggle #143853
Conversation
@elasticmachine merge upstream |
Pinging @elastic/fleet (Team:Fleet) |
Should we allow the user to set that settings programatically in their kibana config file? |
Discussed this with @kpollich and decided not to add to kibana config for now, as it would complicate things - we would have to disable the setting on the UI to avoid getting in inconsistent state with the config. |
@@ -57,7 +57,7 @@ async function deletePackage(name: string, version: string) { | |||
|
|||
async function getAllPackages() { | |||
const res = await fetch( | |||
`${REGISTRY_URL}/search?experimental=true&kibana.version=${KIBANA_VERSION}`, | |||
`${REGISTRY_URL}/search?prerelease=true&kibana.version=${KIBANA_VERSION}`, |
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.
should we try to install the prerelease version of packages here or only the GA ones?
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.
I think we may want to make this configurable but that can probably be done later.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@@ -35,16 +34,13 @@ export async function bulkInstallPackages({ | |||
}: BulkInstallPackagesParams): Promise<BulkInstallResponse[]> { | |||
const logger = appContextService.getLogger(); | |||
|
|||
// auto upgrade to prerelease versions only if the setting is enabled | |||
const prerelease = await getPrereleaseFromSettings(savedObjectsClient); |
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.
removed using the settings after discussing here #122973 (comment)
59c01d9
to
1ff3156
Compare
@@ -100,7 +108,7 @@ export const mapToCard = ({ | |||
fromIntegrations: selectedCategory, | |||
integration: 'integration' in item ? item.integration || '' : '', | |||
name: 'name' in item ? item.name : item.id, | |||
version: 'version' in item ? item.version || '' : '', | |||
version, |
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.
Fixing a bug when a GA version is installed (e.g. endpoint-8.5.0
), the release badge on Installed integrations
tab was showing Beta
. I think this was misleading and the badge should show the installed version's release.
Also, on Browse integrations
tab, changed the integration card to link to the latest version of the integration, not the installed one as currently. Though I am not sure if the intention here was to show the latest or installed version. In main branch, the card shows a link to the installed version, but the version and release badge is based on the latest version, so it is inconsistent.
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.
Also, on Browse integrations tab, changed the integration card to link to the latest version of the integration, not the installed one as currently. Though I am not sure if the intention here was to show the latest or installed version. In main branch, the card shows a link to the installed version, but the version and release badge is based on the latest version, so it is inconsistent.
Should we browse to the installed version from the installed tab and to the latest from the browse all, or it is odd?
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.
Should we browse to the installed version from the installed tab and to the latest from the browse all, or it is odd?
Yeah, this was the most intuitive to me too, this is how it works in the pr currently.
…to show available upgrade if package is installed
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.
Tested locally and it looks good to me 🚀
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Saved Objects .kibana field count
Unknown metric groupsAPI count
ESLint disabled in files
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Summary
Closes #122973
prerelease
toggle toIntegrations
list, disabled by default (meaning that prerelease version packages are filtered out)Pending functionality:
Upgrade available
buttonTest instructions
Option 1: use v2 dev registry which has some prerelease packages
endpoint-8.6.0-dev.0
prerelease version.Option 2: setup local registry
Download the test data zip:
registry-packages.zip
Start a registry:
elastic_agent
package:1.3.5
(GA) and1.3.6-preview
(beta).Checklist