From 1b5f2402de1674b39dc04a73e612f067c29b57a1 Mon Sep 17 00:00:00 2001
From: Samantha Tan <96286575+samantha-t28@users.noreply.github.com>
Date: Tue, 19 Nov 2024 11:38:13 -0800
Subject: [PATCH] fix: Change "Single Account" to "Single Project" in button
text (#200327)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
## Summary
This pull request resolves
[#198879](https://github.com/elastic/kibana/issues/198879), where
"Single Account" was incorrectly displayed in the GCP integration
screen. The text has been updated to "Single Project" to align with GCP
terminology. Additionally, the paragraph above this text was updated to
ensure consistency across the UI.
## Motivation
Aligning the GCP integration screen with GCP’s correct terminology by
replacing "Single Account" with "Single Project" ensures clarity and
consistency across the UI.
## Screenshots:
**Before**: interface showing "Single Account"
**After**: updated interface showing "Single Project"
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [ ]
~~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials~~
- [ ] ~~[Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios~~
- [ ] ~~If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~~
- [ ] ~~This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.~~
- [ ] ~~[Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed~~
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_node:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: Maxim Kholod
(cherry picked from commit a5831c0d2346d7ea7b95cb0516ff67da46b9d68b)
---
.../components/fleet_extensions/policy_template_form.tsx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/x-pack/plugins/cloud_security_posture/public/components/fleet_extensions/policy_template_form.tsx b/x-pack/plugins/cloud_security_posture/public/components/fleet_extensions/policy_template_form.tsx
index 73d8ed22011dc..9d8deb5b9892d 100644
--- a/x-pack/plugins/cloud_security_posture/public/components/fleet_extensions/policy_template_form.tsx
+++ b/x-pack/plugins/cloud_security_posture/public/components/fleet_extensions/policy_template_form.tsx
@@ -148,7 +148,7 @@ const getGcpAccountTypeOptions = (isGcpOrgDisabled: boolean): CspRadioGroupProps
{
id: GCP_SINGLE_ACCOUNT,
label: i18n.translate('xpack.csp.fleetIntegration.gcpAccountType.gcpSingleAccountLabel', {
- defaultMessage: 'Single Account',
+ defaultMessage: 'Single Project',
}),
testId: 'gcpSingleAccountTestId',
},
@@ -377,7 +377,7 @@ const GcpAccountTypeSelect = ({