| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-06-04 |
known issues, known limitations |
secure-enterprise |
{{site.data.keyword.attribute-definition-list}}
{: #known-issues}
Known issues and limitations include configuration management, user access to projects, and identity and access management (IAM) limits. {: shortdesc}
{: #auth-known-issue}
To work in a project, users must have access to the {{site.data.keyword.cloud_notm}} Projects service, the resource group for the project, and {{site.data.keyword.bplong}}. For more information about access, see Assigning users access to projects.
Authorizing projects to deploy to a target account is managed by passing an API key into the deployable architecture. Projects can be directly authorized by using a trusted profile, but trusted profiles are not currently supported by all services. API keys will continue to be supported, but a trusted profile is the preferred method for authorizing deployment to target accounts.
{: #configuration-known-issue}
Configurations can be added, deleted, and renamed. Moving a configuration between projects must be done manually by editing project.json documents on both projects. If there are multiple configurations in a project, they can be organized only by naming conventions.
{: #cost-estimate-known-issue}
Cost estimation is available for deployable architectures in the {{site.data.keyword.cloud_notm}} catalog. Depending on the deployable architecture, a starting cost is estimated based on the available data. This estimated amount is subject to change as the architecture is customized within a project, and it does not include all resources, usage, licenses, fees, discounts, or taxes. For more information, see Estimating architecture costs in a project.
{: #api-sdk-tf-known-issue}
The projects API, SDK, and Terraform functionalities are beta for this release. Beta products are made solely available for evaluation and testing purposes. There are no warranties, SLAs, or support provided and beta products are not intended for production use.
{{../account/known-issues.md#iam_limits}}
{{../account/known-issues.md#cbr-limits}}
{: #enterprise-limits}
The following table lists the maximum limits for {{site.data.keyword.cloud_notm}} enterprises. These limits apply to any user who can create an enterprise, add accounts to an enterprise, or create and update account groups.
| Resource | Max |
|---|---|
| Account groups per enterprise | 500 |
| Accounts per enterprise | 1000 |
| {: caption="Table 3. Enterprise limits" caption-side="top"} |
{{../account/known-issues.md#policy-version-limit}}
{: #drift-detection-known-issue}
Schematics and Terraform can detect a drift only between a changed resource and the specific configuration that created that resource during deployment. The service can’t detect drift in reused or referenced resources.
For example, in a specific scenario, configuration config-1 created a Cloud Object Storage instance during deployment. Later, you deployed configurations config-2 and config-3, and they reused the same Cloud Object Storage instance. When you renamed the resource, drift was detected only between config-1 and the renamed Cloud Object Storage instance. config-2 and config-3 failed the drift detection job because drift can be detected only between a configuration and the resource that it created, not reused.
For more information, see Managing drift.