You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/installation/on-premises/on-prem-feature-management.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,10 +80,10 @@ The table describes the features you can open for Codefresh accounts, in alphabe
80
80
|`gitopsAppGroups`| When enabled, allows users to group GitOps applications by annotations, and view these applications in the Groups tab of the GitOps Apps dashboard. <br>See[Application Groups for GitOps applications]({{site.baseurl}}/docs/deployments/gitops/gitops-app-groups/).| TRUE|
81
81
|`gitopsImageReporting`|Relevant to ProjectOne.<br>When enabled, reports images created with Codefresh Pipelines to the Images dashboard. <br>See[Images in Codefresh]({{site.baseurl}}/docs/dashboards/images/).| FALSE|
82
82
|`hideCompositionsMenuItem`| When enabled, does not show Compositions within Artifacts & Insights in the sidebar of the Codefresh UI.| FALSE|
83
-
|`injectClusterListFromPipelineSettings`| When enabled, turns on the pipeline setting**Kubernetes cluster context pipeline injection** for the account. Individual users can then selectively inject clusters for pipelines from those to which they they access.<br><br> This feature requires the users to have the Update Cluster permission. If not granted, then this feature has no impact when enabled. <br>See[Enabling cluster-contexts for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#enabling-cluster-contexts-for-pipelines).| FALSE|
83
+
|`injectClusterListFromPipelineSettings`| When enabled, turns on the pipeline setting**Kubernetes cluster context pipeline injection** for the account. Individual users can then selectively inject clusters for pipelines from those to which they they access.<br><br> This feature requires the users to have the Update Cluster permission. If not granted, then this feature has no impact when enabled. <br>See[Enabling cluster-contexts for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#kubernetes-cluster-contexts-for-pipelines).| FALSE|
84
84
|`logMasking`|When enabled, secrets in build logs, both online and offline logs, are masked and replaced by asterisks. <br><br>This feature is currently available only for Enterprise customers.|FALSE|
85
85
|`parallelKubectlOperations`|When enabled, allows running parallel steps that includes`kubectl`. Especially Helm`install` and`deploy` steps that deploy to multiple clusters with`kubectl` in parallel.|FALSE|
86
-
|`pipelineScopes`| When enabled, enables Codefresh administrators to configure the API scopes for pipelines at account level. All pipelines in the account inherit these scopes. Codefresh administrators can also override these scopes for individual pipelines.<br>See[Configure pipelinescopes]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#configure-pipeline-scopes).| TRUE|
86
+
|`pipelineScopes`| When enabled, enables Codefresh administrators to configure the API scopes for pipelines at account level. All pipelines in the account inherit these scopes. Codefresh administrators can also override these scopes for individual pipelines.<br>See[Pipelinescopes]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#pipeline-scopes).| TRUE|
87
87
|`promotionFlow`| New feature currently in development.<br>When enabled, allows you to drag an application in the GitOps Product dashboard from its current Environment to a different Environment and trigger a promotion flow.| FALSE|
88
88
|`promotionWorkflows`| New feature currently in development.<br>When enabled, allows you create and run workflows when a promotion is triggered.| FALSE|
89
89
|`restrictedGitSource`| When enabled, allows you to create a Restricted Git Source in addition to a standard Git Source. <br>See[Managing Git Sources in GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/)| FALSE|