You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Wednesday, February 15, 2017, we began releasing a new version of Apigee Edge for Public
Cloud.

> [!NOTE]
> **Note:** **Private Cloud customers** : Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see [About release
> numbering](https://docs.apigee.com/release/apigee-edge-release-process) to understand how you can figure it out by comparing release numbers.
>
> **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
>
> **Release notifications** : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes)

## Deprecations and retirements

The following features are being deprecated or retired. See the [Edge deprecation policy](https://docs.apigee.com/release/deprecation) for more information. See [Apigee deprecations and retirements](https://docs.apigee.com/release/deprecated-features) for the dates around
which features will be retired (removed from the product).

### Apigee secure store (vaults)

The Apigee secure
store, also known as "vaults," is being deprecated and will be retired a year from the
deprecation announcement date shown on the
[Deprecations and
retirements page](https://docs.apigee.com/release/deprecated-features#deprecationsandretirements). Vaults, which provide encrypted storage of key/value pairs, are created
with the management API and accessed at runtime with functions in the apigee-access
Node.js module.

Instead of using the secure store, use encrypted key value maps (KVMs), as described in
[Working with key value maps](https://docs.apigee.com/api-platform/cache/key-value-maps).
Encrypted KVMs are just as secure as vaults and provide more options for creation and
retrieval. (MGMT-3848)

## New features and updates

Following are the new features and updates in this release.

### Shared flows zero-downtime
deployment

When you want to deploy shared flows and ensure that little or no incoming traffic is rejected
during deployment, you can now use a zero-downtime deployment management API. The process is
almost identical to [zero-downtime deployment for API proxies using the management API](https://docs.apigee.com/api-platform/deploy/deploy-api-proxies-using-management-api#seamless). The only
difference is the management API resource.

The following call deploys the shared flow revision indicated in the URI, then undeploys the
previously deployed revision (the `override=true` query parameter enables this):

```
curl -X POST -H "Content-type:application/x-www-form-urlencoded" \
https://api.enterprise.apigee.com/v1/o/{org_name}/environments/{env-name}/sharedflows/{shared_flow_name}/revisions/{revision_number}/deployments?"override=true" \
-u email:password
```

(MGMT-3485)

## Bugs fixed

The following bugs are fixed in this release. This list is primarily for users checking to see
if their support tickets have been fixed. It's not designed to provide detailed information for
all users.

| Issue ID | Description |
|---|---|
| MGMT-3697 | **Management API slow performance** |
| MGMT-3674 | **Unable to create encrypted KVM or Vaults for HIPAA-enabled orgs** |
| MGMT-3647 | **User role access for users with Capitalized email throws 403** |
| MGMT-3601 | **Error when deploying new Apigee proxy** |
| MGMT-3527 | **Load Target server, Cache, VirtualHost error during deployment** |
| DOS-4008 | **Traffic logging bug showing inaccurate drop in traffic** |