External platform extensions in a multi-tenant environment
First Claim
Patent Images
1. A method comprising:
- defining, in a first config file based on a file schema, an access rule for a feature of a service in a cloud environment;
creating, by a computing system of a service provider system, an empty config file based on the first config file, wherein the empty config file contains headers based on the first config file and the empty config file contains no configuration entries;
providing, by the computing system of the service provider system, to a computing device external to the service provider system, the empty config file to enable editing of the empty config file at the computing device;
determining, by the computing system, a change to the empty config file based on editing of the empty config file at the computing device;
creating, by the computing system, a delta file comprising the change to the empty config file, wherein the change is identified as defining a service access of the feature of the service;
modifying, by the computing system, an archive formatted file that is included in a library of class files, wherein the archive formatted file is modified to include the created delta file;
creating, by the computing system, a unified config file having the feature of the service, wherein the unified config file is created by merging the delta file with the first config file;
reading, by the computing system, the unified config file; and
in response to reacting the unified config file, instantiating, by the computing system, an object for the feature of the service using the unified config file.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods and systems are described for allowing third party developers to add extensions to a cloud service provider'"'"'s software as a service (SaaS) services by editing an ‘empty’ config file according to a schema provided by the cloud service provider to form a delta file and then merging the delta file with an internal, full version of the config file. The full config file is then used to initialize and instantiate objects upon a restart of the cloud provider'"'"'s services.
55 Citations
20 Claims
-
1. A method comprising:
-
defining, in a first config file based on a file schema, an access rule for a feature of a service in a cloud environment; creating, by a computing system of a service provider system, an empty config file based on the first config file, wherein the empty config file contains headers based on the first config file and the empty config file contains no configuration entries; providing, by the computing system of the service provider system, to a computing device external to the service provider system, the empty config file to enable editing of the empty config file at the computing device; determining, by the computing system, a change to the empty config file based on editing of the empty config file at the computing device; creating, by the computing system, a delta file comprising the change to the empty config file, wherein the change is identified as defining a service access of the feature of the service; modifying, by the computing system, an archive formatted file that is included in a library of class files, wherein the archive formatted file is modified to include the created delta file; creating, by the computing system, a unified config file having the feature of the service, wherein the unified config file is created by merging the delta file with the first config file;
reading, by the computing system, the unified config file; andin response to reacting the unified config file, instantiating, by the computing system, an object for the feature of the service using the unified config file. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A system comprising:
-
at least one processor; a memory accessible to the at least one processor, the memory storing instructions executable by the at least one processor to perform operations comprising; defining, in a first config file based on a file schema, an access rule for a feature of a service in a cloud environment; creating an empty config file based on the first config file, wherein the empty config file contains headers based on the first config file and the empty config file contains no configuration entries; providing, by a service provider system, to a computing device external to the service provider system, the empty config file to enable editing of the empty config file at the computing device; determining a change to the empty config file based on editing of the empty config file at the computing device; creating a delta file comprising the change to the empty config file, wherein the change is identified as defining a service access of the feature of the service; modifying an archive formatted file that is included in a library of class files, wherein the archive formatted file is modified to include the created delta file; creating a unified config file having the feature of the service, wherein the unified config file is created by merging the delta file with the first config file; reading the unified config file; and in response to reading the unified config file, instantiating an object for the feature of the service using the unified config file. - View Dependent Claims (12, 13, 14, 15, 16)
-
-
17. A non-transitory machine-readable tangible medium storing instructions for causing one or more machines of a service provider system to perform operations comprising:
-
defining, in a first config file based on a file schema, an access rule for a feature of a service in a cloud environment; creating an empty config file based on the first config file, wherein the empty config file contains headers based on the first config file and the empty config file contains no configuration entries; providing to a computing device external to the service provider system, the empty config file to enable editing of the empty config file at the computing device;
determining a change to the empty config file based on editing of the empty config file at the computing device;creating a delta file comprising the change to the empty config file, wherein the change is identified as defining a service access of the feature of the service; modifying an archive formatted file that is included in a library of class files, wherein the archive formatted file is modified to include the created delta file; creating a unified config file having the feature of the service, wherein the unified config file is created by merging the delta file with the first config file; reading the unified config file; and in response to reading the unified config file, instantiating an object for the feature of the service using the unified config file. - View Dependent Claims (18, 19, 20)
-
Specification