Thanks for all the responses.

On Sat, Nov 28, 2015 at 11:26 PM, Imesh Gunaratne <im...@apache.org> wrote:

>
>
> On Fri, Nov 27, 2015 at 6:34 AM, Isuru Haththotuwa <isu...@apache.org>
> wrote:
>>
>>
>>    1. Prior to the first clone, take a backup of the artifacts in the
>>    local repository path to a temporary location
>>    2. When the signup is removed, clean all the artifacts which had been
>>    cloned to the local repository path location (from the git repository 
>> which
>>    was provided when signing up), and restore the artifacts (copy them back
>>    from the backup location to local repository path)
>>
>> This will ensure the state of the instance after removal of the signup is
>> equivalent to the state before the signup was created. WDYT?
>>
>
> AFAIU this issue is specific for Carbon based servers/cartridges.
> Therefore it should be handled in the cartridge using an extension, this
> might be the ADC extension point. The actual problem has occurred because
> of having hot deployable configuration files inside the artifact deployment
> folder of super tenant. This may not happen for other tenants as they start
> with a blank folder for tenant artifacts.
>
IMHO we should not have to implement anything specific for carbon servers.
If there are any artifacts initially, take a backup of those. If there are
no artifacts, no need to take a backup. And there might be scenarios where
the same thing can be used in non-carbon servers as well, after signup is
removed. WDYT?

>
> +1 for the suggestion. I do not see any problem of taking a backup of
> those files. It should only do once, and files may only take few kilobytes
> of disk space.
>
> Thanks
>
> --
> Imesh Gunaratne
>
> Senior Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>

Reply via email to