--- schema_version: "1" id: 74b300dd4da89122bd1095e176fe781952e4fb2de6fb68a257ff2cc007cf306c title: Upgrading PDK collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/pdk/1.6/policies-pdk-upgrade-pdk.md canonical_url: https://docs.mulesoft.com/pdk/1.6/policies-pdk-upgrade-pdk source_site: docs.mulesoft.com content_type: documentation content_hash: 8a3932211e0c765a3f22a15b9ae810827aefca2776acdb05ec7b701ceee75ae9 description: MuleSoft Documentation Site release: "1.6" latest: false --- --- product: Omni Gateway Policy Development Kit (PDK) version: 1.6 --- # Upgrading PDK > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To update a custom policy project, you must update each of these separately versioned Flex Gateway Policy Development Kit (PDK) components: - Anypoint CLI PDK plugin - PDK Rust libraries - Anypoint Cargo plugin - Policy Rust Version - WASI Crate When you upgrade your Anypoint CLI PDK plugin, you must manually upgrade the PDK Rust libraries and Anypoint Cargo plugin to be compatible with the new plugin version. All the PDK custom policies on your device use the same Anypoint CLI PDK plugin. When you create a new custom policy project, the PDK Rust libraries and Anypoint Cargo plugin versions are the same as the Anypoint CLI PDK plugin used to create the project and are independent from other policy projects. To upgrade a custom policy project created with an earlier version of the Anypoint CLI PDK plugin: 1. [Upgrade the Anypoint CLI PDK Plugin](#anypoint-cli-pdk-plugin) 2. [Upgrade the PDK Rust Libraries](#pdk-rust-libraries) 3. [Upgrade the Anypoint Cargo Plugin](#anypoint-cargo-plugin) 4. [Upgrade a Policy’s Rust Version](#anypoint-rust-version) 5. [Upgrade a Policy’s WASI Crate](#anypoint-wasi-crate) ## Upgrade the Anypoint CLI PDK Plugin When editing a custom policy created with an earlier plugin version, ensure your [PDK Rust libraries](#pdk-rust-libraries) and [Anypoint Cargo plugin](#anypoint-cargo-plugin) match your Anypoint CLI PDK plugin version. To upgrade your Anypoint CLI PDK plugin to the latest version, execute the following command: ```ssh anypoint-cli-v4 plugins:install anypoint-cli-pdk-plugin ``` To verify your current plugin version, execute the following command: ```ssh anypoint-cli-v4 plugins ``` For example, the following PDK plugin version is `1.6.0`: ```ssh anypoint-cli-pdk-plugin 1.6.0 ├─ anypoint-cli-command 1.5.2 │ └─ @oclif/plugin-help 5.1.12 └─ @oclif/plugin-version 1.0.4 ``` ## Upgrade the PDK Rust Libraries The PDK Rust library is the Rust code library used by a specific custom policy. Different custom policies might use different PDK library versions. To upgrade the PDK Rust code libraries, modify the `pdk` `dependency` and `pdk-test` `dev-dependency` versions in the `cargo.toml` file of the custom policy. The `pdk` and `pdk-test` versions must match and your Anypoint CLI PDK plugin must support the specified version. In the following example, both dependency versions are `1.6.0`. Modify it to your required version: ```toml [dependencies] pdk = { version = "1.6.0" } [dev-dependencies] pdk-test = { version = "1.6.0" } ``` ## Upgrade the Anypoint Cargo Plugin The Anypoint Cargo plugin extends the functionality of Cargo for use with the PDK Rust Libraries. To upgrade your Anypoint Cargo plugin: 1. Open the `Makefile` of your custom policy. 2. Find the `install-cargo-anypoint` target, for example: install-cargo-anypoint: cargo install cargo-anypoint@1.6.0 3. Change the version after the `@` character to the required version. 4. Save the `Makefile`. 5. Execute the `make setup` command: ```ssh make setup ``` > [!NOTE] Executing the `make setup` command for a certain policy installs that policy’s > Anypoint Cargo plugin version. 6. Execute the following command to verify the correct version is installed: ```ssh cargo anypoint --version ``` ## Upgrade a Policy’s Rust Version To upgrade your Policy’s Rust version: 1. Ensure the Rust version is downloaded on your device. To update Rust, see [Rust Requirements for Using PDK](https://docs.mulesoft.com/pdk/1.6/policies-pdk-prerequisites#rust-requirements). 2. Open the `cargo.toml` of your custom policy. 3. Find your Rust version. For example: rust-version = "1.87.0" 4. Update your Rust version. For example: rust-version = "1.88.0" 5. Save the `cargo.toml` file. ## Upgrade a Policy’s WASI Crate To upgrade your Rust WebAssembly System Interface (WASI) Crate from `wasm32-wasi` to `wasm32-wasip1`: 1. Open the `Makefile` of your custom policy. 2. Find this line: TARGET := wasm32-wasi 3. Replace `wasm32-wasi` with `wasm32-wasip1`: TARGET := wasm32-wasip1 4. Save the `Makefile`. 5. Open the `tests/common/mod.rs` of your custom policy. 6. Find the this line: pub const POLICY\_DIR: &str = concat!(env!("CARGO\_MANIFEST\_DIR"), "/target/wasm32-wasi/release"); 7. Replace `wasm32-wasi` with `wasm32-wasip1`: pub const POLICY\_DIR: &str = concat!(env!("CARGO\_MANIFEST\_DIR"), "/target/wasm32-wasip1/release"); 8. Save the `mod.rs` file. ## Upgrade Policies with Versions Earlier Than 1.6.0 In PDK 1.6.0, the PDK libraries moved from the Anypoint platform to [crates.io](https://crates.io/crates/pdk). When upgrading from versions earlier than 1.6.0, you must update the dependencies to point to the new location. To upgrade policies with versions earlier than 1.6.0: 1. [Upgrade the Anypoint CLI PDK plugin](#anypoint-cli-pdk-plugin). 2. [Upgrade the PDK Rust libraries](#anypoint-rust-version). 3. Upgrade the PDK Rust libraries: 1. Locate the `dependencies` and `dev-dependencies` in your policy’s `cargo.toml`: ```toml [dependencies] pdk = { version = "1.5.0", registry = "anypoint" } [dev-dependencies] pdk-test = { version = "1.5.0", registry = "anypoint" } ``` 2. Update the version and remove the `registry = "anypoint"`: ```toml [dependencies] pdk = { version = "1.6.0" } [dev-dependencies] pdk-test = { version = "1.6.0" } ``` 3. Save the `cargo.toml` file. 4. Upgrade the Anypoint Cargo Plugin: 1. Open the `Makefile` of your custom policy. 2. Find the `install-cargo-anypoint` target, for example: install-cargo-anypoint: cargo install cargo-anypoint@1.5.0 --registry anypoint --config .cargo/config.toml 3. Update the version and remove the `--registry` and `--config` flags: install-cargo-anypoint: cargo install cargo-anypoint@1.6.0 4. Save the `Makefile` file. 5. Remove the Anypoint Platform registry references from your `setup` command: 1. Open the `Makefile` of your custom policy. 2. Find the `setup` target, for example: .PHONY: setup setup: registry-creds login install-cargo-anypoint ## Setup all required tools to build cargo fetch 3. Remove the Anypoint Platform registry references: .PHONY: setup setup: install-cargo-anypoint ## Setup all required tools to build cargo fetch 4. Delete the `login` and `registry-creds` targets. For example: To find an example of the targets, see the [`login` and `registry-creds` targets in the Certification Policy](https://github.com/mulesoft/pdk-custom-policy-examples/blob/1.5.0/certs/Makefile#L68-L85). 5. Save the `Makefile` file. 6. Execute `make setup` to install the updated versions. ## See Also - [Prerequisites for Flex Gateway Policy Development Kit (PDK)](https://docs.mulesoft.com/pdk/1.6/policies-pdk-prerequisites)