You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This policy can be used when a human and/or browser-friendly URL should be transformed into the URL format expected by the web service. This policy only needs to be applied when exposing an alternative URL format, such as clean URLs, RESTful URLs, user-friendly URLs or SEO-friendly URLs that are purely structural URLs that don't contain a query string and instead contain only the path of the resource (after the scheme and the authority). This is often done for aesthetic, usability, or search engine optimization (SEO) purposes.
19
+
Use this policy when you need to transform a human-friendly or browser-friendly URL into the URL format expected by the web service. Apply this policy only when exposing an alternative URL format, such as clean URLs, RESTful URLs, user-friendly URLs, or SEO-friendly URLs that are purely structural and don't contain a query string but instead contain only the path of the resource (after the scheme and the authority). You often make this change for aesthetic, usability, or search engine optimization (SEO) purposes.
|template|The actual web service URL with any query string parameters. Policy expressions are allowed. When expressions are used, the whole value must be an expression. |Yes|N/A|
39
-
|copy-unmatched-params|Specifies whether query parameters in the incoming request not present in the original URL template are added to the URL defined by the rewrite template. Policy expressions are allowed.|No|`true`|
35
+
|copy-unmatched-params|Specifies whether query parameters in the incoming request that aren't present in the original URL template are added to the URL defined by the rewrite template. Policy expressions are allowed.|No|`true`|
40
36
41
37
## Usage
42
38
@@ -46,21 +42,34 @@ This policy can be used when a human and/or browser-friendly URL should be trans
46
42
47
43
### Usage notes
48
44
49
-
You can only add query string parameters using the policy. You can't add extra template path parameters in the rewrite URL.
45
+
You can only add query string parameters by using the policy. You can't add extra template path parameters in the rewritten URL.
46
+
47
+
## Examples
48
+
49
+
### Example 1: Basic URL rewrite
50
+
51
+
In the following example, the public URL is rewritten to match the backend service URL format, and query parameters are included based on other logic.
50
52
51
-
## Example
53
+
- Public URL - `http://api.example.com/storenumber/ordernumber`
In the following example, the public URL is rewritten to match the backend service URL format, and the policy copies any unmatched query parameters to the new URL.
72
+
64
73
```xml
65
74
<!-- Assuming incoming request is /get?a=b&c=d and operation template is set to /get?a={b} -->
66
75
<policies>
@@ -73,7 +82,12 @@ You can only add query string parameters using the policy. You can't add extra t
73
82
</outbound>
74
83
</policies>
75
84
<!-- Resulting URL will be /put?c=d -->
85
+
76
86
```
87
+
### Example 3: Don't copy unmatched parameters
88
+
89
+
In the following example, the public URL is rewritten to match the backend service URL format, and the policy drops any unmatched query parameters.
90
+
77
91
```xml
78
92
<!-- Assuming incoming request is /get?a=b&c=d and operation template is set to /get?a={b} -->
79
93
<policies>
@@ -88,6 +102,20 @@ You can only add query string parameters using the policy. You can't add extra t
88
102
<!-- Resulting URL will be /put -->
89
103
```
90
104
105
+
### Example 4: Use policy expression in the template
106
+
107
+
In the following example, the policy uses expressions in the template to construct the request to the backend.
Copy file name to clipboardExpand all lines: articles/backup/azure-data-lake-storage-backup-support-matrix.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,8 +26,8 @@ Vaulted backups of Azure Data Lake Storage are available in the following region
26
26
27
27
| Availability type | Region |
28
28
| --- | --- |
29
-
|**General availability**| Central US, East Asia, France South, Germany West Central, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India, Central India, North Central US, South India, UK South, West Central US, West US 3, North Europe. |
30
-
|**Preview**|Australia East, East US, East US 2, Southeast Asia, West US, West US 2.|
29
+
|**General availability**| Australia East, Central US, East Asia, France South, Germany West Central, Southeast US, Switzerland North, Switzerland West, UAE North, UK West, West India, Central India, North Central US, South India, UK South, West Central US, West US 3, West Europe, North Europe, West US, West US 2. |
30
+
|**Preview**| EastUS, East US 2, Southeast Asia. |
Copy file name to clipboardExpand all lines: articles/partner-solutions/informatica/overview.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,9 @@
1
1
---
2
2
title: What is Informatica Intelligent Data Management Cloud?
3
-
description: Learn about using the Informatica Intelligent Data Management Cloud.
3
+
description: Learn about using the Informatica Intelligent Data Management Cloud, an Azure Native Service. This article describes key capabilities.
4
4
ms.topic: overview
5
-
ms.date: 01/17/2024
5
+
ms.date: 12/10/2025
6
+
#Customer intent: As an information professional, I want to understand how to manage my Informatica organization as an Azure Native Service.
6
7
---
7
8
8
9
# What is Informatica Intelligent Data Management Cloud?
@@ -15,11 +16,11 @@ You can find Informatica Intelligent Data Management Cloud in the [Azure portal]
15
16
16
17
Use this offering to manage your Informatica organization as an Azure Native Service. You can easily run and manage Informatica Organizations and advanced serverless environments as you need and get started through Azure Clients.
17
18
18
-
You can set up the Informatica organization through a resource provider named `Informatica.DataManagement`. You create and manage the billing, resource creation, and authorization of Informatica resources through the Azure Clients. Informatica owns and runs the Software as a Service (SaaS) application including the Informatica organizations created.
19
+
You can set up the Informatica organization through a resource provider named `Informatica.DataManagement`. Create and manage the billing, resource creation, and authorization of Informatica resources through the Azure Clients. Informatica owns and runs the Software as a Service (SaaS) application including the Informatica organizations created.
19
20
20
21
Here are the key capabilities provided by the Informatica integration:
21
22
22
-
-**Onboarding** of Informatica Intelligent Data Management Cloud (IDMC) as an integrated service on Azure.
23
+
-**Onboarding** of Informatica Intelligent Data Management Cloud (IDMC) as an integrated service on Azure.
23
24
-**Unified billing** of Informatica through Azure Marketplace.
24
25
-**Single-Sign on to Informatica** - No separate sign-up needed from Informatica's IDMC portal.
25
26
-**Create advanced serverless environments** - Ability to create Advanced Serverless Environments from Azure Clients.
@@ -32,12 +33,12 @@ Here are the key capabilities provided by the Informatica integration:
Copy file name to clipboardExpand all lines: articles/storage/container-storage/container-storage-release-notes.md
+17-7Lines changed: 17 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,13 +17,12 @@ This article provides the release notes for Azure Container Storage. It's import
17
17
The following Azure Container Storage versions are supported:
18
18
19
19
| Milestone | Status |
20
-
|----|----------------|
20
+
|-----------|--------|
21
21
|2.0.0 - Major Release | Supported |
22
+
|1.4.0 - Minor Release | Supported |
22
23
|1.3.2 - Patch Release | Supported |
23
24
|1.3.1 - Patch Release | Supported |
24
25
|1.3.0 - Minor Release | Supported |
25
-
|1.2.1 - Patch Release | Supported |
26
-
|1.2.0 - Minor Release | Supported |
27
26
28
27
## Unsupported versions
29
28
@@ -52,6 +51,16 @@ A **major release** introduces significant changes, often including new features
52
51
53
52
There are significant breaking changes in version 2.0.0. Users looking to migrate from version 1.x.x to version 2.0.0 should completely [remove prior versions](remove-container-storage-version-1.md) of Azure Container Storage and review the new setup guides to get started.
54
53
54
+
## Version 1.4.0
55
+
56
+
### Improvements and issues that are fixed
57
+
58
+
- Resolved security vulnerabilities through component updates.
59
+
- Introduced pre-upgrade and post-upgrade hooks for the Azure SAN CSI driver to better manage the CSI driver and volume attachments, ensuring seamless upgrades and preventing resource leaks.
60
+
- Fixed an issue with the etcd watcher that could cause disk pools to remain in the "Creating" status after an upgrade.
61
+
- Renamed mutating and validating webhooks to more specific names to avoid potential naming conflicts.
62
+
- Extended end-of-life support for the v1.x release series.
63
+
55
64
## Version 1.3.2
56
65
57
66
### Improvements and issues that are fixed
@@ -66,7 +75,7 @@ There are significant breaking changes in version 2.0.0. Users looking to migrat
66
75
### Improvements and issues that are fixed
67
76
68
77
-**Bug fixes and recovery improvements**: We made important updates to make etcd recovery stable and reliable. Now, the process includes enhanced retries making cluster restoration smoother and easier to manage. We fixed bugs in Azure Disks and Azure Elastic SAN storage pool creation and addressed upgrade failures caused by Kubernetes job name length limits. To improve reliability, this release fixes a failure during Azure Container Storage extension installation with Azure Elastic SAN. The issue was caused by a missing etcd certificate. Now, etcd components are only deployed when needed.
69
-
-**Expanded platform compatibility and scheduling fixes**: To improve scheduling accuracy, this release ensures Azure Container Storage pods are no longer placed on Windows nodes in mixed OS clusters. We fixed this by enforcing node affinity rules. Additionally, we added support for Elastic SAN on Azure Linux 3.0 nodes.
78
+
-**Expanded platform compatibility and scheduling fixes**: To improve scheduling accuracy, this release ensures Azure Container Storage pods are no longer placed on Windows nodes in mixed OS clusters. We fixed this issue by enforcing node affinity rules. Additionally, we added support for Elastic SAN on Azure Linux 3.0 nodes.
70
79
-**Safeguards to prevent storage pool deletion**: Measures are implemented to prevent the deletion of storage pools with existing persistent volumes when created through custom storage classes.
71
80
72
81
## Version 1.3.0
@@ -123,12 +132,13 @@ Azure Container Storage follows a transparent and predictable support lifecycle,
123
132
-**Patch releases**: Have the same end of life as the subsequent major/minor release.
124
133
125
134
| Release version | Release Date | End of Life | Supported Kubernetes Versions |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments