Skip to content

Commit aefc056

Browse files
yoshi-code-botyoshi-code-bot
authored
Regenerate firebaseappcheck client (#8053)
Generated in GitHub action: https://togithub.com/googleapis/googleapis/google-api-php-client-services/actions/workflows/codegen.yaml
1 parent ab5ea7b commit aefc056

2 files changed

Lines changed: 66 additions & 56 deletions

File tree

‎src/Firebaseappcheck/GoogleFirebaseAppcheckV1ResourcePolicy.php‎

Lines changed: 34 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -20,39 +20,44 @@
2020
class GoogleFirebaseAppcheckV1ResourcePolicy extends \Google\Model
2121
{
2222
/**
23-
* Firebase App Check is not enforced for the service, nor are App Check
24-
* metrics collected. Though the service is not protected by App Check in this
25-
* mode, other applicable protections, such as user authorization, are still
26-
* enforced. An unconfigured service is in this mode by default.
23+
* The relevant App Check protection is not enforced for the service or
24+
* resource, nor are App Check metrics collected. Though the relevant App
25+
* Check protection is not applied, other applicable protections, such as user
26+
* authorization, are still enforced. An unconfigured protection is in this
27+
* mode by default.
2728
*/
2829
public const ENFORCEMENT_MODE_OFF = 'OFF';
2930
/**
30-
* Firebase App Check is not enforced for the service. App Check metrics are
31-
* collected to help you decide when to turn on enforcement for the service.
32-
* Though the service is not protected by App Check in this mode, other
33-
* applicable protections, such as user authorization, are still enforced.
34-
* Some services require certain conditions to be met before they will work
35-
* with App Check, such as requiring you to upgrade to a specific service
36-
* tier. Until those requirements are met for a service, this `UNENFORCED`
37-
* setting will have no effect and App Check will not work with that service.
31+
* The relevant App Check protection is not enforced for the service or
32+
* resource. App Check metrics are collected to help you decide when to turn
33+
* on enforcement. These metrics will show the portion of traffic that is
34+
* deemed invalid by the relevant App Check protection, but that traffic will
35+
* not be rejected until you turn on enforcement. Though the relevant App
36+
* Check protection is not enforced, other applicable protections, such as
37+
* user authorization, are still enforced. Some services require certain
38+
* conditions to be met before they will work with App Check, such as
39+
* requiring you to upgrade to a specific service tier. Until those
40+
* requirements are met for a service, this `UNENFORCED` setting will have no
41+
* effect and App Check will not work with that service.
3842
*/
3943
public const ENFORCEMENT_MODE_UNENFORCED = 'UNENFORCED';
4044
/**
41-
* Firebase App Check is enforced for the service. The service will reject any
42-
* request that attempts to access your project's resources if it does not
43-
* have valid App Check token attached, with some exceptions depending on the
44-
* service; for example, some services will still allow requests bearing the
45-
* developer's privileged service account credentials without an App Check
46-
* token. App Check metrics continue to be collected to help you detect issues
47-
* with your App Check integration and monitor the composition of your
48-
* callers. While the service is protected by App Check, other applicable
49-
* protections, such as user authorization, continue to be enforced at the
50-
* same time. Use caution when choosing to enforce App Check on a Firebase
51-
* service. If your users have not updated to an App Check capable version of
52-
* your app, their apps will no longer be able to use your Firebase services
53-
* that are enforcing App Check. App Check metrics can help you decide whether
54-
* to enforce App Check on your Firebase services. If your app has not
55-
* launched yet, you should enable enforcement immediately, since there are no
45+
* The relevant App Check protection is enforced for the service or resource.
46+
* The service or resource will reject any traffic not accompanied by an App
47+
* Check token that is deemded valid by the relevant protection. There are
48+
* some exceptions depending on the service; for example, some services will
49+
* still allow requests bearing the developer's privileged service account
50+
* credentials without an App Check token. App Check metrics continue to be
51+
* collected to help you detect issues with your App Check integration and
52+
* monitor the composition of your callers. While the service is protected by
53+
* App Check, other applicable protections, such as user authorization,
54+
* continue to be enforced at the same time. Use caution when choosing to
55+
* enforce App Check protections. If your users have not updated to a version
56+
* of your app that meets the requirements of the relevant App Check
57+
* protection, their app may stop working. App Check metrics can help you
58+
* decide whether to enforce App Check on your services and resources. If your
59+
* app has not launched yet, you should enable enforcement as soon as you
60+
* verify that your App Check implementation is correct, since there are no
5661
* outdated clients in use. Some services require certain conditions to be met
5762
* before they will work with App Check, such as requiring you to upgrade to a
5863
* specific service tier. Until those requirements are met for a service, this
@@ -62,7 +67,7 @@ class GoogleFirebaseAppcheckV1ResourcePolicy extends \Google\Model
6267
public const ENFORCEMENT_MODE_ENFORCED = 'ENFORCED';
6368
/**
6469
* Required. The App Check enforcement mode for this resource. This will
65-
* override the EnforcementMode setting on the service.
70+
* override the App Check overall EnforcementMode setting on the service.
6671
*
6772
* @var string
6873
*/
@@ -110,7 +115,7 @@ class GoogleFirebaseAppcheckV1ResourcePolicy extends \Google\Model
110115

111116
/**
112117
* Required. The App Check enforcement mode for this resource. This will
113-
* override the EnforcementMode setting on the service.
118+
* override the App Check overall EnforcementMode setting on the service.
114119
*
115120
* Accepted values: OFF, UNENFORCED, ENFORCED
116121
*

‎src/Firebaseappcheck/GoogleFirebaseAppcheckV1Service.php‎

Lines changed: 32 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -20,39 +20,44 @@
2020
class GoogleFirebaseAppcheckV1Service extends \Google\Model
2121
{
2222
/**
23-
* Firebase App Check is not enforced for the service, nor are App Check
24-
* metrics collected. Though the service is not protected by App Check in this
25-
* mode, other applicable protections, such as user authorization, are still
26-
* enforced. An unconfigured service is in this mode by default.
23+
* The relevant App Check protection is not enforced for the service or
24+
* resource, nor are App Check metrics collected. Though the relevant App
25+
* Check protection is not applied, other applicable protections, such as user
26+
* authorization, are still enforced. An unconfigured protection is in this
27+
* mode by default.
2728
*/
2829
public const ENFORCEMENT_MODE_OFF = 'OFF';
2930
/**
30-
* Firebase App Check is not enforced for the service. App Check metrics are
31-
* collected to help you decide when to turn on enforcement for the service.
32-
* Though the service is not protected by App Check in this mode, other
33-
* applicable protections, such as user authorization, are still enforced.
34-
* Some services require certain conditions to be met before they will work
35-
* with App Check, such as requiring you to upgrade to a specific service
36-
* tier. Until those requirements are met for a service, this `UNENFORCED`
37-
* setting will have no effect and App Check will not work with that service.
31+
* The relevant App Check protection is not enforced for the service or
32+
* resource. App Check metrics are collected to help you decide when to turn
33+
* on enforcement. These metrics will show the portion of traffic that is
34+
* deemed invalid by the relevant App Check protection, but that traffic will
35+
* not be rejected until you turn on enforcement. Though the relevant App
36+
* Check protection is not enforced, other applicable protections, such as
37+
* user authorization, are still enforced. Some services require certain
38+
* conditions to be met before they will work with App Check, such as
39+
* requiring you to upgrade to a specific service tier. Until those
40+
* requirements are met for a service, this `UNENFORCED` setting will have no
41+
* effect and App Check will not work with that service.
3842
*/
3943
public const ENFORCEMENT_MODE_UNENFORCED = 'UNENFORCED';
4044
/**
41-
* Firebase App Check is enforced for the service. The service will reject any
42-
* request that attempts to access your project's resources if it does not
43-
* have valid App Check token attached, with some exceptions depending on the
44-
* service; for example, some services will still allow requests bearing the
45-
* developer's privileged service account credentials without an App Check
46-
* token. App Check metrics continue to be collected to help you detect issues
47-
* with your App Check integration and monitor the composition of your
48-
* callers. While the service is protected by App Check, other applicable
49-
* protections, such as user authorization, continue to be enforced at the
50-
* same time. Use caution when choosing to enforce App Check on a Firebase
51-
* service. If your users have not updated to an App Check capable version of
52-
* your app, their apps will no longer be able to use your Firebase services
53-
* that are enforcing App Check. App Check metrics can help you decide whether
54-
* to enforce App Check on your Firebase services. If your app has not
55-
* launched yet, you should enable enforcement immediately, since there are no
45+
* The relevant App Check protection is enforced for the service or resource.
46+
* The service or resource will reject any traffic not accompanied by an App
47+
* Check token that is deemded valid by the relevant protection. There are
48+
* some exceptions depending on the service; for example, some services will
49+
* still allow requests bearing the developer's privileged service account
50+
* credentials without an App Check token. App Check metrics continue to be
51+
* collected to help you detect issues with your App Check integration and
52+
* monitor the composition of your callers. While the service is protected by
53+
* App Check, other applicable protections, such as user authorization,
54+
* continue to be enforced at the same time. Use caution when choosing to
55+
* enforce App Check protections. If your users have not updated to a version
56+
* of your app that meets the requirements of the relevant App Check
57+
* protection, their app may stop working. App Check metrics can help you
58+
* decide whether to enforce App Check on your services and resources. If your
59+
* app has not launched yet, you should enable enforcement as soon as you
60+
* verify that your App Check implementation is correct, since there are no
5661
* outdated clients in use. Some services require certain conditions to be met
5762
* before they will work with App Check, such as requiring you to upgrade to a
5863
* specific service tier. Until those requirements are met for a service, this

0 commit comments

Comments
 (0)