[Fleet] Add flag for prerelease to templates/inputs endpoint #174471
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/ci |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
criamico
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
nchaulet
reviewed
Jan 9, 2024
x-pack/test/fleet_api_integration/apis/epm/get_templates_inputs.ts
Outdated
Show resolved
Hide resolved
nchaulet
approved these changes
Jan 9, 2024
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @criamico |
kilfoyle
approved these changes
Jan 9, 2024
nreese
pushed a commit
to nreese/kibana
that referenced
this pull request
Jan 10, 2024
…#174471) Fixes elastic#172667 ## Summary Some of the integrations show directly the prerelease version of the package in the overview section, but this wasn't happening in the "configs" section. Here I'm adding a flag to the `templates/{pkgName}/{pkgVersion}/inputs` endpoint that allows to select the prerelease tag as well: ``` GET kbn:api/fleet/epm/templates/{pkgName}/{pkgVersion}/inputs?format=yaml&prerelease=true ``` One example is the Istio package: ``` GET kbn:api/fleet/epm/templates/istio/0.5.0/inputs?format=yaml&prerelease=true ``` ### Istio overview - before  ### Istio overview - after  ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Jan 11, 2024
…#174471) Fixes elastic#172667 ## Summary Some of the integrations show directly the prerelease version of the package in the overview section, but this wasn't happening in the "configs" section. Here I'm adding a flag to the `templates/{pkgName}/{pkgVersion}/inputs` endpoint that allows to select the prerelease tag as well: ``` GET kbn:api/fleet/epm/templates/{pkgName}/{pkgVersion}/inputs?format=yaml&prerelease=true ``` One example is the Istio package: ``` GET kbn:api/fleet/epm/templates/istio/0.5.0/inputs?format=yaml&prerelease=true ``` ### Istio overview - before  ### Istio overview - after  ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Feb 15, 2024
…#174471) Fixes elastic#172667 ## Summary Some of the integrations show directly the prerelease version of the package in the overview section, but this wasn't happening in the "configs" section. Here I'm adding a flag to the `templates/{pkgName}/{pkgVersion}/inputs` endpoint that allows to select the prerelease tag as well: ``` GET kbn:api/fleet/epm/templates/{pkgName}/{pkgVersion}/inputs?format=yaml&prerelease=true ``` One example is the Istio package: ``` GET kbn:api/fleet/epm/templates/istio/0.5.0/inputs?format=yaml&prerelease=true ``` ### Istio overview - before  ### Istio overview - after  ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #172667
Summary
Some of the integrations show directly the prerelease version of the package in the overview section, but this wasn't happening in the "configs" section. Here I'm adding a flag to the
templates/{pkgName}/{pkgVersion}/inputsendpoint that allows to select the prerelease tag as well:One example is the Istio package:
Istio overview - before
Istio overview - after
Checklist