After you enable a custom WebAssembly plug-in on a cloud-native gateway, the plug-in becomes read-only and cannot be edited directly. To apply changes to plug-in logic without disabling the plug-in, release a new version and switch to it.
Prerequisites
Before you begin, make sure that you have:
A cloud-native gateway. For more information, see Create a cloud-native gateway
A custom WebAssembly plug-in deployed on the gateway
Release a new plug-in version
Log on to the MSE console and select a region in the top navigation bar.
In the left-side navigation pane, choose Cloud-native Gateway > Gateways. On the Gateways page, click the name of your gateway.
In the left-side navigation pane, click Plug-in Marketplace.
On the All Plug-ins tab, click the Custom subtab.
Click the
icon on the plug-in card and select Release New Version.In the Release New Plug-in panel, configure the following parameters and click OK.
Parameter Description Plug-in Name A unique name for the plug-in. Plug-in Description A description displayed on the plug-in card. WebAssembly Language The programming language used to develop the plug-in. WebAssembly File The compiled .wasmbinary file. Upload the file from your local machine.Configuration Verification The fields and expected values to verify when the plug-in starts. If the plug-in does not require configuration, leave the code editor blank. Plug-in Execution Stage The processing phase for the plug-in. Stages run in the following order: Authorization > Authentication > Statistics > Default. Select Default if the plug-in has no ordering dependency on other plug-ins. Plug-in Execution Priority The priority within the selected stage. A higher value means higher priority. Keep the default value if ordering does not matter. For custom values, use multiples of 10.
Switch to the new version
After the new version is released:
Click the plug-in card to open its details.
On the Plug-in Configuration tab, select the destination version.
Click Update Version.