Add CDN Fallbacks to UI Pages #140
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
sanchitmehta
force-pushed
the
user/sanmeht/CDNFallBack
branch
from
27d12c6 to
dae9133
Compare
sanchitmehta
force-pushed
the
user/sanmeht/CDNFallBack
branch
from
dae9133 to
8a3fab9
Compare
JennyLawrance
approved these changes
Oct 21, 2020
sanchitmehta
added a commit
that referenced
this pull request
Jan 14, 2021
* Add a silent try catch while printing previous log tail (#87) * Added console event generator for kudu (#85) * Fixed the bug where symlinks couldn't be created for zip extraction + (#84) added recursive permissions change for zip deploy/zip controller * ANT84 Linux Consumption Remote Build Patch (#88) * ANT84 Linux Consumption Server Side Build Patch * Add logger for dependencies * Remove zip context validation * Fix error message when doing zip deploy with WEBSITE_RUN_FROM_PACKAGE * Add ability to grab the FRAMEWORK_VERSION for function apps (#91) * Kudu Fixes (#90) * Using Log4Net to generate kudu event logs * Added lts support for Oryx on NODE. Made compressing python packages default. Fixed minor bugs with kudu event logs * Changed the log path in Log4Net config * Added Express Build support for NETCore. Added a filter to avoid excessive logging for certain paths. * Modified python compress arguments * Added debug arguments for oryx build * Added a fix for NETCore express build scenario + Removing Oryx Manifest file for Zip Deploy * Minor change * Fix python 3.7 path in Oryx Build (#92) * Fix python 3.7 path * Fix syntax * Fix missing Docker logs (#96) * Fix missing Docker logs * Retrieve logs for the last seven days from the latest timestamp * Added KuduConsole Log4Net logger + Some Bug Fixes (#97) * Added log4net support for KuduConsole * Fix FileNotFound exception for LogStream Service * Fix Oryx Build command not picking up the version * ANT86 add zipdeploy endpoint support for ARM call (#94) * Add zipdeploy endpoint for ANT86 * Remove ZipDeployController * ANT86 Patch on Linux Consumption Remote Build (#95) * Warm up linux conusmption function app after remote build * Also take SCM_RUN_FROM_PACKAGE from app setting * Trigger a recycle after wardeploy (#98) * Trigger a recycle after wardeploy - This is a port of this PR - projectkudu/kudu#3050 - from the Kudu repo. - Current implementation of /wardeploy triggers a recycle of container, only on Xenon and Linux. This recycle is performed using the restartTrigger.txt file. - This commit adds support to /wardeploy for triggering a recycle of classic Windows web apps in addition to just Xenon and Linux, if the app setting WEBSITE_RECYCLE_PREVIEW_ENABLED is defined. Besides, the recyle will be performed using the /api/app/restart API. - The new behavior is hidden behind a WEBSITE_RECYCLE_PREVIEW_ENABLED flag, which is added only temporarily. This flag will eventually be removed and the new behavior will become the default. * Incorporated CR comment * Kudu Fixes + Enhancements - Oct (#101) * Adding some trace to zip formation * Added Artifacts support as a flag * Fix broken Deployments for Node 12.9 and remove Oryx Symlink Files on Zip Deploy (#102) * Fixing node_modules symlink deletion + * Add support to remove the symlink file using rm * Fix Node 10.16/12.9 broken deployments * Add Intermediate directory support for PHP (#103) * Update function app language version regex to take account lengthy function version (#108) * Add SyncTriggers query param for zipdeploy in Linux Consumption (#106) * Update deeplink to Linux troubleshoot page Same change as projectkudu/kudu#3139 * Added NoOpBuilder for static site stack (#115) * Added NoOpBuilder * Use FRAMEWORK env variable to choose NoOpBuilder * Check for NoOpBuilder before check for Oryx builder * Parse external deployment ID from zip push headers * Persist new ID through changeset so it carries over to later deployment steps * Make usage consistent across all push deploy types * Fix ruby language detection * [Linux Consumption] Support persistent storage using Azure file share (#121) Adds support for creating & mounting Azure file shares for Linux consumption scm sites. Function apps can opt-in using the app setting ENABLE_KUDU_PERSISTENT_STORAGE=1. Currently the persistent storage is used for deplpyment logs only. This change also moves artifacts location from /deployments path to its own path /artifacts. * [ANT 88] Implement force remote build in Linux Consumption (#109) * Implement force remote build endpoint call * Rename ForceRemoteBuild to OverwriteWebsiteRunFromPackage * Fix merge conflict * Fix Log4Net config for KuduConsole telemetry (#123) * DynamicInstall Post-Recieve Hook Fix (#126) * Fixed Dynamic Install Environment for Kudu Post Recieve Hook for Local Git * More fixes * Add a message on memory limit when running remote build (#127) * Log events with actual sitename in Linux LinuxConsumption (#125) Since Linux consumption containers start in placeholdermode the initially cached sitename should be refreshed once the container is specialized * fixed TryGetValues to TryGetValue and changed result data type * Kudu to FE call to update deployment status Comment resolution Added build failure when exception is thrown * OneDeploy API - /publish and /api/publish (#134) * OneDeploy API - /publish and /api/publish - Adds a new /publish and /api/publish APIs for Java deployment scenarios - This new API primarily supports Java scenarios currently, but can be easily extended for additional scenarios - Overview of new changes - OneDeploy reuses bulk of the code from PushDeploymentController and DeploymentManager - OneDeployBuilder is a new OneDeploy specific site builder, OneDeployFetch is a OneDeploy specific Fetch handler - WatchedFileEnabled/RestartAllowed/ArtifactType/TargetRootPath are additional knobs introduced in DeploymentInfoBase.cs for OneDeploy specific functionality - The implementation inspects the WEBSITE_STACK environment variable for certain scenarios. This variable is injected by the App Service runtime - OneDeploy uses the new restart API (in other words, it does not rely on touching any file for triggering a recycle) - Summary of changes to existing code: - A bunch of variables were renamed for readability purposes - ZipDeploymentInfo is now ArtifactDeploymentInfo (generalized) and is now used by OneDeploy for non-zip artifacts as well - Note: This is primarily a port of projectkudu/kudu#3203 with some additional enhancements to OneDeploy. These enhancements will be back ported to https://github.com/projectkudu/kudu * Minor refactoring * Remove merge conflict artifact * Clean up formatting and avoid posting deployment status if not using fixed deployment ID * Refactor helper function for retrieving ID from request * Refactor to commit deployment ID to NullRepository and use strings for deployment status constants * Fix whitespace changes * Revert "Fix whitespace changes" This reverts commit 5f2be3c. * Revert changes to IRepo and HgRepo * Add back IRepo and HgRepo with correct line endings * Added retry logic to retry 3 times with 5sec intervals (#137) * Adde retry logic to retry 3 times with 5sec intervals * Fail silently logic for handling 404 * Removed extra call on build failed No need of the extra query param Comment resolution Removed extra logging * Self cert changes * Fixed build errors * Revert "Fixed build errors" This reverts commit 8306c58. * Build fix * Throw exception if request was throttled * Throw exception if request was throttled * PR feedback * Add home page for Linux Consumption app (#138) * Add home page for Linux Consumption app * Use partial page * Address PR issues * Update DeploymentId to ExternalDeploymentId * Fix typo in pushdeploymentcontroller * Add CDN Fallbacks (#140) * Fail silently if call to /api/app/updatedeploystatus fails (#146) * Fix LinuxConsumption HomePage for Controller Ping (#143) * Add endpoint for checking SCM site * Simplify if statement * Add more resilience to '/api/deployments/` endpoints for continued polling (#141) * Add retries to ensure deployment doesn't fail at these steps * Added rettries at various places * Adjust retry timeouts * Lock Improvements test * Handled CR comments * Adding --compress-destination-dir for Python builds (#145) * Changed python oryx build args to --compress-destination-dir Removed extra -p Removed zip extensions since they aren't needed anymore * Removed unnecessary zip extensions * fail update status API silently if 3 retries fail * Fixed debug console (#150) * adding filemanager to newui (#151) * Moving first request to Kudu in update deployment status api * Hiding KeyVault secrets on Environment page (#155) * Hiding KeyVault secret environment variables with checkbox * Adding key vault hiding secrets to NewUI Co-authored-by: Kar Shin Lin <karslin@microsoft.com> * Add GitHub Action Builds integration for the Pull Requests (#162) * Create dotnet-core.yml Add GH Action for build and tests * Rename workflow file * Rename workflow files * Rename dev merge build (#163) * Update README.md Add Build Status Badge * Add LGTM Confiugration file (#164) * Changing net core version to 2.2.8 (#165) * Update .lgtm.yml * update1 (#169) * Fixes for ZipDeploy, Status lock conflict (#173) * Add more tracing + fix zipdeploy regression (#167) * Add more tracing + fix zipdeploy regression * Add a retry to get deployment lock * Revert Purge codepath * Revert * Actual fix * If KUDU_BUILD_VERSION is set to 0.0.1 do python ANT90 build (#168) Creating constants for the app setting Trim whitespace for the app setting * Fix file handle leak for status.lock (#170) * Reduce retry count Co-authored-by: purva-vasudeo <61296267+purva-vasudeo@users.noreply.github.com> * NETCore Deployment Fixes for DeploymentV2 (#174) * DeploymentV2 fixes * Minor fixes * Inject external deployment id to response headers (#175) * Add a silent try catch while iterating over docker logs (#176) * OneDeploy improvements - This is a port of projectkudu/kudu#3248 - Allow absolute paths. Earlier implementation only allows relative paths - Allow WAR to be deployed to JBoss EAP (although it is not supported on Windows, this will help consistency with KuduLite) * Block linux consumption health check probes without auth headers (#172) * update1 * Block linux consumption health check probes without auth headers * Block linux consumption health check probes without auth headers * Updating health route (#2) * **BYPASS_SECRET_SCANNING** * Fix cred scan (#179) Co-authored-by: Hanzhang Zeng (Roger) <48038149+Hazhzeng@users.noreply.github.com> Co-authored-by: Ankit Kumar <ankikuma@microsoft.com> Co-authored-by: michimune <michimune@outlook.com> Co-authored-by: Shrirang Shirodkar <shrishrirang@users.noreply.github.com> Co-authored-by: purva-vasudeo <61296267+purva-vasudeo@users.noreply.github.com> Co-authored-by: Jonathan Kleinfeld <jokleinf@microsoft.com> Co-authored-by: JennyLawrance <jennylaw@microsoft.com> Co-authored-by: Bala G <balag@outlook.com> Co-authored-by: Purva Vasudeo <puvasude@microsoft.com> Co-authored-by: anandanthony <anfranci@microsoft.com> Co-authored-by: karshinlin <lin.karshin@gmail.com> Co-authored-by: Kar Shin Lin <karslin@microsoft.com> Co-authored-by: divyagandhii <44176589+divyagandhii@users.noreply.github.com> Co-authored-by: Shrirang Shirodkar <shrirs@microsoft.com>
Hazhzeng
pushed a commit
to Hazhzeng/KuduLite
that referenced
this pull request
Jul 20, 2021
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.
No description provided.