mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #2945] Standard not being created when customer is onboarded via a webhook #1462
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#1462
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 @BNWEIN on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2945
Description
If you use the Partner Webhooks function to automatically onboard a customer, and you have the "Exclude onboarded tenants from Top-Level Standards" option enabled, a new standard with "Do not apply All Tenants Standard to this tenant" should be created when the tenant is onboarded, but that is not happening
Similarly, when you use the "Do not apply All Tenants Standard to this tenant" when using the onboarding URL it also does not create the standard with the option to exclude from top level standard enabled
Environment data
@github-actions[bot] commented on GitHub (Oct 16, 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!".
@BNWEIN commented on GitHub (Oct 16, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Oct 16, 2024):
wontfix, standards v3 solve this.