chore: Change term bitbucket server to bitbucket data center across pac

chaged the term bitbuckt server to bitbucket data center everywhere
in docs, go files, and .sh files.

Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

Author: zakisk

.github/pull_request_template.md

@@ -20,13 +20,13 @@
 
 - If adding a provider feature, fill in the following details:
 
-| Git Provider     | Supported |
-|------------------|-----------|
-| GitHub App       | ✅️        |
-| GitHub Webhook   | ❌️        |
-| Gitea            | ❌️        |
-| GitLab           | ❌️        |
-| Bitbucket Cloud  | ❌️        |
-| Bitbucket Server | ❌️        |
+| Git Provider          | Supported |
+|-----------------------|-----------|
+| GitHub App            | ✅️        |
+| GitHub Webhook        | ❌️        |
+| Gitea                 | ❌️        |
+| GitLab                | ❌️        |
+| Bitbucket Cloud       | ❌️        |
+| Bitbucket Data Center | ❌️        |
 
   (update the documentation accordingly)

docs/content/_index.md

@@ -45,7 +45,7 @@ tracking using a Git workflow.
 
 - Git events Filtering and support for separate pipelines for each event
 
-- GitLab, Bitbucket Server, Bitbucket Cloud and GitHub Webhook support.
+- GitLab, Bitbucket Data Center, Bitbucket Cloud and GitHub Webhook support.
 
 - `tkn-pac` plug-in for Tekton CLI for managing pipelines-as-code repositories and bootstrapping.
 

docs/content/docs/dev/_index.md

@@ -372,6 +372,6 @@ a push to a branch or for a release.
 # Links
 
 - [Jira Backlog](https://issues.redhat.com/browse/SRVKP-2144?jql=component%20%3D%20%22Pipeline%20as%20Code%22%20%20AND%20status%20!%3D%20Done)
-- [Bitbucket Server Rest API](https://docs.atlassian.com/bitbucket-server/rest/7.17.0/bitbucket-rest.html)
+- [Bitbucket Data Center Rest API](https://docs.atlassian.com/bitbucket-server/rest/7.17.0/bitbucket-rest.html)
 - [GitHub API](https://docs.github.com/en/rest/reference)
 - [GitLab API](https://docs.gitlab.com/ee/api/api_resources.html)

docs/content/docs/guide/matchingevents.md

@@ -185,7 +185,7 @@ files.
 ## Matching a PipelineRun on a Regex in a comment
 
 {{< tech_preview "Matching PipelineRun on regex in comments" >}}
-{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="false" bitbucket_server="false" >}}
+{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="false" bitbucket_datacenter="false" >}}
 
 You can trigger a PipelineRun based on a comment on a Pull Request or a [Pushed
 Commit]({{< relref
@@ -235,7 +235,7 @@ relref "/docs/guide/gitops_commands.md#gitops-commands-on-pushed-commits" >}}).
 ## Matching PipelineRun to a Pull Request labels
 
 {{< tech_preview "Matching PipelineRun to a Pull-Request label" >}}
-{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="false" bitbucket_server="false" >}}
+{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="false" bitbucket_datacenter="false" >}}
 
 Using the annotation `pipelinesascode.tekton.dev/on-label`, you can match a
 PipelineRun to a Pull Request label. For example, if you want to match the
@@ -258,7 +258,7 @@ metadata:
 * The `on-event` is still needed to match the Pull Request event on the
   proper targeted event.
 * This annotation is currently supported only on GitHub, Gitea, and GitLab
-  providers. Bitbucket Cloud and Bitbucket Server do not support adding labels
+  providers. Bitbucket Cloud and Bitbucket Data Center do not support adding labels
   to Pull Requests.
 * When you add a label to a Pull Request, the corresponding PipelineRun is
   triggered immediately, and no other PipelineRun matching the same Pull Request

docs/content/docs/guide/policy.md

@@ -9,7 +9,7 @@ Pipelines-as-Code uses policies to control which actions can be performed by
 users who belong to specific teams within an organization, as defined on GitHub
 or other supported Git providers (currently GitHub and Gitea).
 
-{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="false" bitbucket_cloud="false" bitbucket_server="false" >}}
+{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="false" bitbucket_cloud="false" bitbucket_datacenter="false" >}}
 
 ## Supported Actions
 

docs/content/docs/guide/running.md

@@ -120,7 +120,7 @@ click on it and follow the pipeline execution directly there.
 ### Cancelling in-progress PipelineRuns
 
 {{< tech_preview "Cancelling in progress PipelineRuns" >}}
-{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="true" bitbucket_server="false" >}}
+{{< support_matrix github_app="true" github_webhook="true" gitea="true" gitlab="true" bitbucket_cloud="true" bitbucket_datacenter="false" >}}
 
 You can choose to cancel a PipelineRun that is currently in progress. This can
 be done by adding the annotation `pipelinesascode.tekton.dev/cancel-in-progress:

docs/content/docs/install/bitbucket_cloud.md

@@ -135,7 +135,7 @@ $ tkn pac create repo
   Pipelines as code always assumes that it will be in the same namespace where the
   `Repository` has been created.
 
-- The `tkn pac create` and `tkn pac bootstrap` commands are not supported on Bitbucket Server.
+- The `tkn pac create` and `tkn pac bootstrap` commands are not supported on Bitbucket Data Center.
 
 {{< hint info >}}
 You can only reference a user by the `ACCOUNT_ID` in a owner file. For reason see here:

…content/docs/install/bitbucket_server.md …ent/docs/install/bitbucket_datacenter.mddocs/content/docs/install/bitbucket_server.md renamed to docs/content/docs/install/bitbucket_datacenter.md docs/content/docs/install/bitbucket_server.md renamed to docs/content/docs/install/bitbucket_datacenter.md

@@ -1,11 +1,11 @@
 ---
-title: Bitbucket Server
+title: Bitbucket Data Center
 weight: 15
 ---
-# Install Pipelines-As-Code on Bitbucket Server
+# Install Pipelines-As-Code on Bitbucket Data Center
 
 Pipelines-As-Code has a full support of [Bitbucket
-Server](https://www.atlassian.com/software/bitbucket/enterprise).
+Data Center](https://www.atlassian.com/software/bitbucket/enterprise).
 
 After following the [installation](/docs/install/installation):
 
@@ -39,7 +39,7 @@ recreate it.
   echo https://$(oc get route -n pipelines-as-code pipelines-as-code-controller -o jsonpath='{.spec.host}')
   ```
 
-* [Refer to this screenshot](/images/bitbucket-server-create-webhook.png) on
+* [Refer to this screenshot](/images/bitbucket-datacenter-create-webhook.png) on
   which events to handle on the Webhook. The individual events to select are :
 
   * Repository -> Push
@@ -51,7 +51,7 @@ recreate it.
   * Create a secret with personal token in the `target-namespace`
 
   ```shell
-  kubectl -n target-namespace create secret generic bitbucket-server-webhook-config \
+  kubectl -n target-namespace create secret generic bitbucket-datacenter-webhook-config \
     --from-literal provider.token="TOKEN_AS_GENERATED_PREVIOUSLY" \
     --from-literal webhook.secret="SECRET_AS_SET_IN_WEBHOOK_CONFIGURATION"
   ```
@@ -70,16 +70,16 @@ recreate it.
   spec:
     url: "https://bitbucket.com/workspace/repo"
     git_provider:
-      # make sure you have the right bitbucket server api url without the
+      # make sure you have the right bitbucket data center api url without the
       # /api/v1.0 usually the # default install will have a /rest suffix
-      url: "https://bitbucket.server.api.url/rest"
+      url: "https://bitbucket.datacenter.api.url/rest"
       user: "your-bitbucket-username"
       secret:
-        name: "bitbucket-server-webhook-config"
+        name: "bitbucket-datacenter-webhook-config"
         # Set this if you have a different key in your secret
         # key: "provider.token"
       webhook_secret:
-        name: "bitbucket-server-webhook-config"
+        name: "bitbucket-datacenter-webhook-config"
         # Set this if you have a different key for your secret
         # key: "webhook.secret"
 ```
@@ -90,7 +90,7 @@ recreate it.
   Pipelines as code always assumes it will be the same namespace as where the
   repository has been created.
 
-* `tkn-pac create` and `bootstrap` is not supported on Bitbucket Server.
+* `tkn-pac create` and `bootstrap` is not supported on Bitbucket Data Center.
 
 {{< hint danger >}}
 

docs/content/docs/install/global_repositories_setting.md

@@ -102,7 +102,7 @@ means a repository configured using [GitHub webhooks]({{< relref "/docs/install/
 - gitlab
 - gitea
 - bitbucket-cloud
-- bitbucket-server
+- bitbucket-datacenter
 
 The global repository settings for the Git provider can currently only
 reference one type of provider on a cluster. The user would need to specify

docs/content/docs/install/overview.md

@@ -35,5 +35,5 @@ preferences the preferred install method is the GitHub Application method.
 * [GitHub Application](/docs/install/github_apps).
 * [GitHub Webhook](/docs/install/github_webhook)
 * [GitLab](/docs/install/gitlab)
-* [Bitbucket Server](/docs/install/bitbucket_server)
+* [Bitbucket Data Center](/docs/install/bitbucket_datacenter)
 * [Bitbucket Cloud](/docs/install/bitbucket_cloud)