FINERACT-2026: Replace HTTPie with curl in Minikube documentation#5546
Closed
Paula-Arias11 wants to merge 1 commit intoapache:developfrom
Closed
FINERACT-2026: Replace HTTPie with curl in Minikube documentation#5546Paula-Arias11 wants to merge 1 commit intoapache:developfrom
Paula-Arias11 wants to merge 1 commit intoapache:developfrom
Conversation
Contributor
|
No ticket reference, PR title not formatted according to rules, is this your idea? Is this an issue for anyone else? Is this on a Jira ticket? No body knows like this... please fix or withdraw. |
Paula-Arias11
changed the title
6 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The "Using Minikube" section currently uses http (HTTPie), which is not a standard tool and is missing from the REQUIREMENTS section. This causes a command not found error for most developers. This PR replaces it with curl to ensure consistency with the "How to run for local development" section and to remove undocumented dependencies.
Checklist
Write the commit message as per our guidelines
Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
Create/update unit or integration tests for verifying the changes made. (N/A for documentation changes)
Follow our coding conventions.
Add required Swagger annotation and update API documentation... (N/A)
This PR must not be a "code dump". Large changes can be made in a branch, with assistance.