Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes provider 1.0.0 release notes #832

Conversation

linglingye001
Copy link
Contributor

No description provided.


### Breaking Changes
* Schema (more information in [Azure App Configuration Kubernetes Provider reference](https://learn.microsoft.com/en-us/azure/azure-app-configuration/reference-kubernetes-provider?tabs=default)):
* Rename `keyValues` to `configuration`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed

* Rename `keyVaults` to `secret` and put it in the root which is at the same level as `configuration`.
* Rename `secret.auth.vaults` to `secret.auth.keyVaults`.
* Upgrade API version from `v1beta1` to `v1`.
* Add `*.refresh.enabled` property for dynamic configuration. It's required if data is expected to be refreshed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added *.refresh.enabled property for dynamic configuration. It defaults to false and is required if data is expected to be refreshed.

## 1.0.0 - xx xx, 2023

### Breaking Changes
* Schema (more information in [Azure App Configuration Kubernetes Provider reference](https://learn.microsoft.com/en-us/azure/azure-app-configuration/reference-kubernetes-provider?tabs=default)):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Schema update (see [Azure App Configuration Kubernetes Provider reference](https://learn.microsoft.com/azure/azure-app-configuration/reference-kubernetes-provider) for the complete schema):

### Breaking Changes
* Schema (more information in [Azure App Configuration Kubernetes Provider reference](https://learn.microsoft.com/en-us/azure/azure-app-configuration/reference-kubernetes-provider?tabs=default)):
* Rename `keyValues` to `configuration`.
* Rename `keyVaults` to `secret` and put it in the root which is at the same level as `configuration`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed ... and moved it to the root, which ...

* Rename `keyValues` to `configuration`.
* Rename `keyVaults` to `secret` and put it in the root which is at the same level as `configuration`.
* Rename `secret.auth.vaults` to `secret.auth.keyVaults`.
* Upgrade API version from `v1beta1` to `v1`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we move this up before the breaking change?

Released the stable API version v1.

* Renamed `keyValues` to `configuration`.
* Renamed `keyVaults` to `secret` and move it to the root, which is at the same level as `configuration`.
* Renamed `secret.auth.vaults` to `secret.auth.keyVaults`.
* Add `*.refresh.enabled` property for dynamic configuration. It defaults to false and is required if data is expected to be refreshed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the configuration.refresh.enabled property. It defaults to false and must be set to true for dynamic configuration refresh.

@@ -2,6 +2,17 @@

[Image][image] | [Sample][sample]

## 1.0.0 - xx xx, 2023

**Released the stable API version `v1`**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release of the stable API version v1.

@linglingye001 linglingye001 merged commit f955f71 into Azure:main Nov 15, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants