Merge pull request #233 from ScaleSec/current_policies_2023-08-04

policies/org_policy.json

@@ -38,7 +38,7 @@
         {
             "name": "constraints/ainotebooks.requireAutoUpgradeSchedule",
             "displayName": "Require automatic scheduled upgrades on new Vertex AI Workbench user-managed notebooks and instances",
-            "description": "This boolean constraint, when enforced, requires that newly created Vertex AI Workbench user-managed notebooks and instances have an automatic upgrade schedule set. The auto-upgrade schedule can be defined by using the `notebook-upgrade-schedule` metadata flag to specify a cron schedule for the automatic upgrades. For example: `--metadata=notebook-upgrade-schedule=\"00 19 * * MON\"`.",
+            "description": "This boolean constraint, when enforced, requires that newly created Vertex AI Workbench user-managed notebooks and instances have an automatic upgrade schedule set. The automatic upgrade schedule can be defined by using the `notebook-upgrade-schedule` metadata flag to specify a cron schedule for the automatic upgrades. For example: `--metadata=notebook-upgrade-schedule=\"00 19 * * MON\"`.",
             "constraintDefault": "ALLOW",
             "booleanConstraint": {}
         },
@@ -794,14 +794,14 @@
         },
         {
             "name": "constraints/spanner.assuredWorkloadsAdvancedServiceControls",
-            "displayName": "Enable advanced service control for compliance workloads.",
+            "displayName": "Enable advanced service control for compliance workloads",
             "description": "Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. When this boolean constraint is enforced, certain aspects of supportability will be impaired and provisioned resources will strictly follow advanced sovereignty requirements for Assured Workloads. This policy will apply to existing projects, but it will not affect resources that have already been provisioned; ie. modifications to the policy will only be reflected in resources created after the policy is modified.",
             "constraintDefault": "ALLOW",
             "booleanConstraint": {}
         },
         {
             "name": "constraints/spanner.disableMultiRegionInstanceIfNoLocationSelected",
-            "displayName": "Disable Cloud Spanner multi-region if no location selected.",
+            "displayName": "Disable Cloud Spanner multi-region if no location selected",
             "description": "Do not configure or modify this policy. This constraint is automatically configured during Assured Workloads onboarding and is only intended for advanced regulatory control for Assured Workloads. This boolean constraint, when enforced, prevents the creation of spanner instances using multi region instance config unless a location is selected. Cloud Spanner today does not yet support selecting location, so all multi regions will be disallowed. In the future, Spanner will provide the functionality for users to select a location for multi regions. Enforcement of this constraint is not retroactive. Spanner instances that have been already created will be unaffected.",
             "constraintDefault": "ALLOW",
             "booleanConstraint": {}