> ## Documentation Index > Fetch the complete documentation index at: https://docs.domino.ai/llms.txt > Use this file to discover all available pages before exploring further. # Updates a :ref:`ref_flyteidl.admin.NamedEntity` object > Update the fields associated with a NamedEntity ## OpenAPI ````yaml /api-specs/cloud/flyte-native-api.yaml put /api/v1/named_entities/{resource_type}/{id.project}/{id.domain}/{id.name} openapi: 3.0.0 info: title: flyteidl/service/admin.proto version: version not set servers: - url: https://mycluster.domino.tech description: >- Replace 'mycluster.domino.tech' with your Domino cluster hostname. For Domino Cloud customers, that is .domino.tech (e.g., acme.domino.tech). For self-hosted deployments, it is the hostname you reach the Domino UI at. security: [] tags: - name: AdminService paths: /api/v1/named_entities/{resource_type}/{id.project}/{id.domain}/{id.name}: put: tags: - AdminService summary: Updates a :ref:`ref_flyteidl.admin.NamedEntity` object description: Update the fields associated with a NamedEntity operationId: AdminService_UpdateNamedEntity parameters: - name: resource_type description: |- Resource type of the metadata to update +required in: path required: true schema: type: string enum: - UNSPECIFIED - TASK - WORKFLOW - LAUNCH_PLAN - DATASET - name: id.project description: Name of the project the resource belongs to. in: path required: true schema: type: string - name: id.domain description: |- Name of the domain the resource belongs to. A domain can be considered as a subset within a specific project. in: path required: true schema: type: string - name: id.name description: >- User provided value for the resource. The combination of project + domain + name uniquely identifies the resource. +optional - in certain contexts - like 'List API', 'Launch plans' in: path required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/AdminServiceUpdateNamedEntityBody' required: true responses: '200': description: A successful response. content: application/json: schema: $ref: '#/components/schemas/adminNamedEntityUpdateResponse' default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/googlerpcStatus' components: schemas: AdminServiceUpdateNamedEntityBody: type: object properties: id: type: object properties: org: type: string description: Optional, org key applied to the resource. title: |- Identifier of the metadata to update +required metadata: $ref: '#/components/schemas/adminNamedEntityMetadata' description: >- Request to set the referenced named entity state to the configured value. adminNamedEntityUpdateResponse: type: object description: Purposefully empty, may be populated in the future. googlerpcStatus: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/protobufAny' adminNamedEntityMetadata: type: object properties: description: type: string title: |- Common description across all versions of the entity +optional state: $ref: '#/components/schemas/adminNamedEntityState' description: Additional metadata around a named entity. protobufAny: type: object properties: '@type': type: string description: >- A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics. additionalProperties: {} description: >- `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName": } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" } adminNamedEntityState: type: string enum: - NAMED_ENTITY_ACTIVE - NAMED_ENTITY_ARCHIVED - SYSTEM_GENERATED default: NAMED_ENTITY_ACTIVE description: >- The status of the named entity is used to control its visibility in the UI. - NAMED_ENTITY_ACTIVE: By default, all named entities are considered active and under development. - NAMED_ENTITY_ARCHIVED: Archived named entities are no longer visible in the UI. - SYSTEM_GENERATED: System generated entities that aren't explicitly created or managed by a user. ````