Skip to content

Construction Account Admin SDK exposes outdated cloudWorksharing product key #175

Description

@manveer-sohal

ACC Account Admin SDK serializes outdated cloudWorksharing product key

In @aps_sdk/construction-account-admin, the generated ProductKeys object currently exposes:

ProductKeys.AndCloudWorksharing === "and cloudWorksharing"

The current aps-sdk-openapi schema defines the product key as cloudWorksharing:

The affected generated file in this repository is:

The same stale value also appears in the .NET SDK:

Reproduction

The expected property does not compile:

ProductKeys.CloudWorksharing

TypeScript reports:

Property 'CloudWorksharing' does not exist...
Did you mean 'AndCloudWorksharing'?

The specification-correct literal is also rejected by the generated request type:

products: [
  {
    key: "cloudWorksharing",
    access: ProductAccess.Member
  }
]

TypeScript reports that "cloudWorksharing" is not assignable to ProductKeys and suggests "and cloudWorksharing".

Using the only exported SDK member:

products: [
  {
    key: ProductKeys.AndCloudWorksharing,
    access: ProductAccess.Member
  }
]

produces the following serialized request body:

{
  "products": [
    {
      "key": "and cloudWorksharing",
      "access": "member"
    }
  ]
}

also traced the generated request pipeline and intercepted the request before network dispatch, confirming that no serialization layer changes the value.

Affected operations

The same generated ProductKeys type is used by:

  • assignProjectUser
  • importProjectUsers
  • updateProjectUser

Additional context

The current aps-sdk-openapi specification defines the value as "cloudWorksharing" (see decbf987). The generated Node SDK currently appears to expose the previous value, "and cloudWorksharing".

Runtime server behavior has not been tested, so this issue does not claim whether the API rejects, ignores, or continues accepting the older value.

Question for maintainers

Would you prefer this to be addressed by regenerating the Construction Account Admin package from the current OpenAPI specification, or through a targeted compatibility patch?

Quick link reference

What Link
Node SDK stale enum productKeys.ts#L26
Current OpenAPI schema accountadmin.yaml#L4102-L4120
Correcting commit decbf987
.NET SDK stale enum ProductKeys.gen.cs#L130-L133

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions