Azure App Configuration
An Azure service that provides hosted, universal storage for Azure app configurations.
240 questions
Error when Fork this repository and define the Forked repository as the "External GIT" inside our Azure Web app "Deployment Center"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 15%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJJ%3C/text%3E%3C/svg%3E)
john john Pter
360
Reputation points
We have an Azure App Service >> and inside the "Deployment Center" >> "External GIT" >> i define this repo as the external GIT. and i did the deployment and it went successfully.
Now I Forked this repo inside another GItHub repo using those steps:-
- git clone https://github.com/microsoft-teams-operations-center/microsoft-teams-emergency-operations-center.git
- git remote add upstream https://github.com/OfficeDev/microsoft-teams-emergency-operations-center.git
- git remote -v origin https://github.com/microsoft-teams-operations-center/microsoft-teams-emergency-operations-center.git (fetch) origin https://github.com/microsoft-teams-operations-center/microsoft-teams-emergency-operations-center.git (push) upstream https://github.com/OfficeDev/microsoft-teams-emergency-operations-center.git (fetch) upstream https://github.com/OfficeDev/microsoft-teams-emergency-operations-center.git (push)
- git fetch upstream
- git add .
- git commit -m "Your commit message"
- git push origin main
So now the Forked repo got the exact code as the original repo (this repo). But when I defined the Forked repo as the external GIT isndie Azure Web App >> and i do a deployment i got this error:-
Command: deploy.cmd
Restoring npm packages for EOC-TeamsFx (this can take several minutes)
"C:\home\site\repository"
Restoring npm packages for tabs folder (this can take several minutes)
"C:\home\site\repository\EOC-TeamsFx\tabs"
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/abort-controller@2.1.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-auth@1.7.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-client@1.9.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-http-compat@2.1.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-lro@2.7.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-paging@1.6.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-rest-pipeline@1.16.0',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-tracing@1.1.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/core-util@1.9.0',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/keyvault-keys@4.8.0',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/logger@1.1.2',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'lru-cache@10.2.2',
npm WARN EBADENGINE required: { node: '14 || >=16.14' },
npm WARN EBADENGINE current: { node: 'v16.13.0', npm: '8.19.2' }
npm WARN EBADENGINE }
npm notice
up to date in 19s
npm notice New major version of npm available! 8.19.2 -> 10.9.0
276 packages are looking for funding
`npm notice Changelog:
Sign in to answer