config: update precache using main/4.21-RC response #187
Conversation
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
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
✅ Build complete for PR #187. 🔗 Download the cmk binaries (expires on September 04, 2025) |
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
shwstppr
changed the title
DaanHoogland
changed the title
rohityadavcloud
approved these changes
Aug 25, 2025
DaanHoogland
approved these changes
Aug 25, 2025
Contributor
DaanHoogland
left a comment
DaanHoogland
left a comment
There was a problem hiding this comment.
tested against latest RC
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Updates precache to output from a CloudStack repo main branch/4.21 env.
Some API/param descriptions now contain backticks, which break the format in precache.go.
Therefore, instead of adding listApis output as a string variable, store the output in a JSON file and use embed to get it in a Go variable.