Software package sharing to restricted landscapes
In an example embodiment, an alternative technical method for sharing a public package to a restricted landscape that avoids a content manager service (CMS) making a call to a tenant management service (TMS). This overcomes any issues involved with the CMS making the call to the TMS, while still permitting the sharing of public packages within the restricted landscape. More particularly, a poll-pull based mechanism is introduced where the restricted CMS periodically polls and checks for any packages shared with it from a public CMS and, if found, pulls the tenant FQDN from the public CMS. The restricted CMS will then fire a request to the TMS to retrieve the tenant metadata.
1 . A system comprising:
at least one hardware processor; and
a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
periodically sending a request from a restricted content manager service to a public content manager service to check for packages shared with a tenant of a tenant management service associated with the restricted content manager service, the public content manager service having a repository for storage of packages and not directly communicating with the tenant management service;
in response to the periodic sending, receiving tenant metadata for one or more tenants with which the public content manager service determines one or more packages have been shared, the one or more tenants associated with the restricted content manager service;
obtaining, by the restricted content manager service, tenant details from the tenant management service, based on the tenant metadata; and
causing, by the restricted content manager service, the public content manager service to update sharing permissions for one or more tenants corresponding to the tenant details by passing the tenant details to the public content manager service.
2 . The system of claim 1 , wherein the public content manager service stores, for a shared package, package details and tenant details corresponding to one or more tenants with which the package is to be shared in an interim table.
3 . The system of claim 2 , wherein the causing results in the public content manager service updating a permission table with the tenant details.
4 . The system of claim 3 , wherein the causing further results in the public content manager service clearing any entries associated with the package details from the interim table.
5 . The system of claim 1 , wherein the tenant details include a fully qualified domain name (FQDN) of any tenant with which the packages are to be shared.
6 . The system of claim 1 , wherein the tenant metadata includes a uniform unique identifier (UUID) for any tenant with which the packages are to be shared.
7 . The system of claim 2 , wherein the interim table is stored in an in-memory database.
8 . A method comprising:
periodically sending a request from a restricted content manager service to a public content manager service to check for packages shared with a tenant of a tenant management service associated with the restricted content manager service, the public content manager service having a repository for storage of packages and not directly communicating with the tenant management service;
in response to the periodic sending, receiving tenant metadata for one or more tenants with which the public content manager service determines one or more packages have been shared, the one or more tenants associated with the restricted content manager service;
obtaining, by the restricted content manager service, tenant details from the tenant management service, based on the tenant metadata; and
causing, by the restricted content manager service, the public content manager service to update sharing permissions for one or more tenants corresponding to the tenant details by passing the tenant details to the public content manager service.
9 . The method of claim 8 , wherein the public content manager service stores, for a shared package, package details and tenant details corresponding to one or more tenants with which the package is to be shared in an interim table.
10 . The method of claim 9 , wherein the causing results in the public content manager service updating a permission table with the tenant details.
11 . The method of claim 10 , wherein the causing further results in the public content manager service clearing any entries associated with the package details from the interim table.
12 . The method of claim 8 , wherein the tenant details include a fully qualified domain name (FQDN) of any tenant with which the packages are to be shared.
13 . The method of claim 8 , wherein the tenant metadata includes a uniform unique identifier (UUID) for any tenant with which the packages are to be shared.
14 . The method of claim 9 , wherein the interim table is stored in an in-memory database.
15 . A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
periodically sending a request from a restricted content manager service to a public content manager service to check for packages shared with a tenant of a tenant management service associated with the restricted content manager service, the public content manager service having a repository for storage of packages and not directly communicating with the tenant management service;
in response to the periodic sending, receiving tenant metadata for one or more tenants with which the public content manager service determines one or more packages have been shared, the one or more tenants associated with the restricted content manager service;
obtaining, by the restricted content manager service, tenant details from the tenant management service, based on the tenant metadata; and
causing, by the restricted content manager service, the public content manager service to update sharing permissions for one or more tenants corresponding to the tenant details by passing the tenant details to the public content manager service.
16 . The non-transitory machine-readable medium of claim 15 , wherein the public content manager service stores, for a shared package, package details and tenant details corresponding to one or more tenants with which the package is to be shared in an interim table.
17 . The non-transitory machine-readable medium of claim 16 , wherein the causing results in the public content manager service updating a permission table with the tenant details.
18 . The non-transitory machine-readable medium of claim 17 , wherein the causing further results in the public content manager service clearing any entries associated with the package details from the interim table.
19 . The non-transitory machine-readable medium of claim 15 , wherein the tenant details include a fully qualified domain name (FQDN) of any tenant with which the packages are to be shared.
20 . The non-transitory machine-readable medium of claim 15 , wherein the tenant metadata includes a uniform unique identifier (UUID) for any tenant with which the packages are to be shared.