- integration of the security requirements within the bindings
- simplification of the API (after developer feedbacks)
- integration of the security requirements within the bindings
- simplification of the API (after developer feedbacks)
The ***binder*** can run ***bindings*** v1, v2 and/or v3 in any combination.
Thus moving from v1 or v2 to v3 is not enforced at this time. But ...
The ***binder*** can run ***bindings*** v1, v2 and/or v3 in any combination.
Thus moving from v1 or v2 to v3 is not enforced at this time. But ...
of bindings v1 and to deprecate the use of bindings v2.
So at the end, **IT IS HIGHLY NEEDED TO SWITCH TO VERSION 3**
of bindings v1 and to deprecate the use of bindings v2.
So at the end, **IT IS HIGHLY NEEDED TO SWITCH TO VERSION 3**
This guide covers the migration of bindings from version 2 to version 3.
The migration from version 1 is not treated here because bindings version 1
This guide covers the migration of bindings from version 2 to version 3.
The migration from version 1 is not treated here because bindings version 1
-are very old and probably does not exist anymore. If needed you can refer
-to the old [guide to migrate bindings from v1 to v2](legacy/afb-migration-v1-to-v2.md).
+are very old and probably do not exist anymore. If needed you can refer
+to the old [guide to migrate bindings from v1 to v2](legacy/afb-migration-v1-to-v2.html).
SED=migration-to-binding-v3.sed
curl -o $SED $BASE/docs/$SED
sed -i -f $SED file1 file2 file3...
```
SED=migration-to-binding-v3.sed
curl -o $SED $BASE/docs/$SED
sed -i -f $SED file1 file2 file3...
```
This automatic action does most of the boring job but not all the job.
The remaining of this guide explains the missing part.
This automatic action does most of the boring job but not all the job.
The remaining of this guide explains the missing part.