move from closed preview to open preview (#9027)

* Update webhooks.adoc * Update set-up-multiple-configuration-files-for-a-project.adoc * a couple more notes * Update jekyll/_cci2/webhooks.adoc Co-authored-by: Rosie Yohannan <[email protected]> --------- Co-authored-by: Rosie Yohannan <[email protected]>
circleci · Oct 18, 2024 · f41aea2 · f41aea2
1 parent e20f3e3
commit f41aea2
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/jekyll/_cci2/set-up-multiple-configuration-files-for-a-project.adoc b/jekyll/_cci2/set-up-multiple-configuration-files-for-a-project.adoc
@@ -10,7 +10,7 @@ contentTags:
 :icons: font
 :experimental:
 
-NOTE: This feature is generally available for orgs that integrate with CircleCI's GitHub App and is available in "Preview" for orgs that integrate with GitHub via the xref:github-integration#[CircleCI GitHub OAuth App]. See our link:https://discuss.circleci.com/t/product-update-multiple-configuration-files-per-project/50637[community forum] to request access.  To find out which GitHub account type you have, see the xref:github-apps-integration#[GitHub App integration] page.
+NOTE: This feature is generally available for orgs that integrate with CircleCI's GitHub App and is available in "Preview" for orgs that integrate with GitHub via the xref:github-integration#[CircleCI GitHub OAuth App]. See our link:https://discuss.circleci.com/t/product-update-multiple-configuration-files-per-project/50637[community forum] for details on the "Preview".  To find out which GitHub account type you have, see the xref:github-apps-integration#[GitHub App integration] page.
 
 You can use multiple configuration files in a CircleCI project and set up separate triggers for each one. Each configuration triggers a separate pipeline on a trigger event. If your existing configuration file is getting too large to manage, consider splitting it into multiple files.
 
@@ -19,7 +19,7 @@ You can use multiple configuration files in a CircleCI project and set up separa
 
 To use multiple configuration files for a project in CircleCI, you will need to meet the following prerequisites:
 
-* A CircleCI account connected to your code in GitHub, integrated through our xref:github-apps-integration#[GitHub App]. You can link:https://circleci.com/signup/[sign up for free]. If you have an existing CircleCI account connected through the GitHub OAuth app, request access to the "preview" for this feature on the link:https://discuss.circleci.com/t/product-update-multiple-configuration-files-per-project/50637[community forum].
+* A CircleCI account connected to your code in GitHub, integrated through our xref:github-apps-integration#[GitHub App]. You can link:https://circleci.com/signup/[sign up for free]. 
 * A project set up in CircleCI that you want to configure with multiple configuration files. See the xref:create-project#[Create a project in CircleCI] page for steps.
 
 [#add-additional-config-file]
@@ -41,7 +41,6 @@ Next, add a new pipeline in your CircleCI project settings.
 . Find your project in the list, select the ellipsis (icon:ellipsis-h[]) next to it and select **Project Settings**
 . Select **Pipelines** in the sidebar
 +
-TIP: If you do not see **Pipelines** in the sidebar, your project is integrated using either xref:github-integration#[GitHub OAuth] or xref:bitbucket-integration#[Bitbucket Cloud] and support for this feature is not yet available. For GitHub OAuth app integrations you can request preview access, see the note at the top of this page.
 . Select btn:[Add Pipeline] (or btn:[Set Up Pipeline] for GitHub OAuth app integrations)
 . Complete the required form fields:
 ** Give your pipeline a descriptive name
@@ -57,7 +56,6 @@ Next, create a trigger for your pipeline.
 
 . Following from the previous step, select **Triggers** in the sidebar
 +
-TIP: If you do not see **Triggers** in the sidebar, your project is integrated using either xref:github-integration#[GitHub OAuth] or xref:bitbucket-integration#[Bitbucket Cloud] and support for this feature is not yet available. For GitHub OAuth app integrations you can request preview access, see the note at the top of this page.
 . Select btn:[Add Trigger]
 . Select **GitHub App** in the dropdown menu
 . Select btn:[Next]

diff --git a/jekyll/_cci2/webhooks.adoc b/jekyll/_cci2/webhooks.adoc
@@ -17,7 +17,7 @@ Setting up an **outbound webhook** on CircleCI enables your third party service
 
 Setting up an inbound webhook (as a **custom webhook** trigger) on CircleCI enables a third party service to trigger a CircleCI pipeline. Any service that can send a webhook or make a `curl` request can trigger a CircleCI pipeline.
 
-NOTE: Selecting a custom webhook as a pipeline trigger is generally available for orgs that integrate with CircleCI's GitHub App, and is available in "Preview" for orgs that integrate with GitHub via the CircleCI xref:github-integration#[GitHub OAuth App]. See our link:https://discuss.circleci.com/t/trigger-pipelines-from-anywhere-custom-webhooks-now-in-preview/49864[community forum] to request access.  To find out which GitHub account type you have, see the xref:github-apps-integration#[GitHub App integration] page.
+NOTE: Selecting a custom webhook as a pipeline trigger is generally available for orgs that integrate with CircleCI's GitHub App, and is available in "Preview" for orgs that integrate with GitHub via the CircleCI xref:github-integration#[GitHub OAuth App]. To find out which GitHub account type you have, see the xref:github-apps-integration#[GitHub App integration] page.
 
 == Custom webhooks
 
@@ -42,7 +42,9 @@ NOTE: When triggering via `curl`, you must use a `POST` request with `content-ty
 curl -X POST -H "content-type: application/json" 'https://internal.circleci.com/private/soc/e/<your-URL>?secret=<your-secret>'
 ----
 
-See our link:https://discuss.circleci.com/t/trigger-pipelines-from-anywhere-inbound-webhooks-now-in-preview/49864[community forum] for more details or how to use this functionality with a link:https://discuss.circleci.com/t/re-build-automatically-when-new-image-is-available-on-dockerhub/50350[3rd party service like DockerHub].
+See our link:https://discuss.circleci.com/t/trigger-pipelines-from-anywhere-inbound-webhooks-now-in-preview/49864[community forum] for more details or how to use this functionality with a link:https://discuss.circleci.com/t/re-build-automatically-when-new-image-is-available-on-dockerhub/50350[3rd party service like DockerHub]. 
+
+NOTE: Custom webhooks will not work with xref:contexts#security-goup-restrictions[security group restrictions].  Additionally, the configuration file that is used for pipelines triggered by a custom webhook will only be visible in the CircleCI web app if the configuration file path is `.circleci/config.yml`.
 
 === Example: Trigger one pipeline from another