Hope I'm not adding noise here. *Option 1* suggested by Lakmali(Coping all
sequences from the old pack and then replacing them with the new ones)
would be best because it would also prevent the issues(such as API
referring to non existing sequence) that might come up if for some reason
an already e
Can we use a diff library [1] to patch the changes of the new release to
existing customize files. We can create a diff/patch file containing the
changes we did from last release and when we migrate use
the java-diff-utils to apply that patch file to existing files. This way
even if there are custo
Hi Nuwan, I was only referring to using this to move the synapse configs
over, since users need to copy these over manually currently. But if there
is no value in doing it this way then its fine. I understand that the
exported API package has a lot more information that we dont really need
for this
On 13 January 2016 at 18:34, Lakmali Baminiwatta wrote:
> If we don't involve migration client to handle this, AFAIU we have below
> approaches.
>
> 1. If they don't have customizations:
>
>- Option 1: Copy everything from old synapse config to new synapse
>config. Later replace default
On Wed, Jan 13, 2016 at 8:28 PM, Uvindra Dias Jayasinha
wrote:
> @Lakmali, +1, we can do it this way.
>
>
> @All, just a suggestion for next time, it would be great if we could
> leverage the API Import/Export feature to move existing APIs over to the
> new product version, since its available in
@Lakmali, +1, we can do it this way.
@All, just a suggestion for next time, it would be great if we could
leverage the API Import/Export feature to move existing APIs over to the
new product version, since its available in the product. Users dont need to
manually copy them over then. WDYT?
On 13
Ya this is fine but it has a real impact on complicating the migration.
This issue has been there with migrating previous releases as well. We need
to put more thought into reducing migration complexity when we add new
features, more complications means more issues to deal with and lots of
time con
If we don't involve migration client to handle this, AFAIU we have below
approaches.
1. If they don't have customizations:
- Option 1: Copy everything from old synapse config to new synapse
config. Later replace default sequences, apis of ST and tenants from the
latest resources.
- O
On Wed, Jan 13, 2016 at 6:07 PM, Uvindra Dias Jayasinha
wrote:
> Ok if we allow these to be extended then we should not be adding our logic
> from the product here, but seems that we have made improvements within the
> extensible part.
>
They are being modified for extending the extension suppor
According to the current instructions, latest sequences get replaced by the
old sequences. So what I am suggesting is that we can assume that it's the
responsibility of the person who does the migration to add the
customizations to latest default sequences which reside in
repository/resources/apim-
Ok if we allow these to be extended then we should not be adding our logic
from the product here, but seems that we have made improvements within the
extensible part.
We should add our changes to a default sequence that is used unless it has
been overridden by a custom sequence that has been defin
On Wed, Jan 13, 2016 at 5:51 PM, Uvindra Dias Jayasinha
wrote:
> I think the only way is to complicate the migration instructions,
>
> If user has customized any sequences they need to copy them over manually
> to latest pack and we will use those.(Discalimer to user: You maybe missing
> out on t
I think the only way is to complicate the migration instructions,
If user has customized any sequences they need to copy them over manually
to latest pack and we will use those.(Discalimer to user: You maybe missing
out on the latest changes shipped with the default sequences in the latest
pack)
On Wed, Jan 13, 2016 at 3:30 PM, Lakmali Baminiwatta
wrote:
> Hi all,
>
> In our migration guide, currently what we instruct is to copy & replace
> repository/deployment/server/synapse-config/default directory and
> repository/tenants from previous APIM version to new APIM version. Here we
> ment
Hi all,
In our migration guide, currently what we instruct is to copy & replace
repository/deployment/server/synapse-config/default directory and
repository/tenants from previous APIM version to new APIM version. Here we
mention to skip replacing _TokenAPI_.xml, _RevokeAPI_.xml and
_AuthorizeAPI_
15 matches
Mail list logo
