mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2753] Click to deploy: ResourceDeploymentFailure #1366
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1366
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EnterfusionFL on GitHub (Jul 31, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2753
Description
When using the "Deploy to Azure" button for the cipp installation I receive the following error:
Error details: {"code":"ResourceDeploymentFailure","target":"/subscriptions/{subId}/resourceGroups/cipp/providers/Microsoft.Web/sites/cipprbtsk/sourcecontrols/web","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."}
I triple checked my input repository URLs and Github token, everything looks exactly as it should according to the install guide.
Environment data
@github-actions[bot] commented on GitHub (Jul 31, 2024):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@KelvinTegelaar commented on GitHub (Jul 31, 2024):
Support issue, support is only for sponsors.
@EnterfusionFL commented on GitHub (Aug 1, 2024):
Account upgraded to sponsor. Please re-open.
@modhash commented on GitHub (Aug 27, 2024):
I have the same issue and i tried it in 2 separate azure accounts, i believe the selfhosted deployment is broken.