Website: use latest version information from dogfood for Fleet maintained apps pages. #26619
+23
−6
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
eashaw
requested review from
lukeheath,
georgekarrv and
sharon-fdm
as code owners
fleet-release
approved these changes
Feb 26, 2025
lukeheath
approved these changes
Feb 27, 2025
|
@lukeheath Thanks for approving this. I didn't realize that the dogfood API token stored in GH secrets does not have permission to send requests to the |
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.
Closes: #24379
Changes:
build-static-contentscript to accept a new input:dogfoodAccessToken. If provided, the script will pull the latest version information for Fleet maintained apps from Fleet's dogfood instance when the website deploys.test-websiteanddeploy-fleet-websiteworkflows to pass in the dogfood API token secret to thebuild-static-contentscript