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

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions releaseNotes/KubernetesProvider.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

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

## 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):

* 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`.
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 `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.

* 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-preview4 - September 14, 2023

### New Features
Expand Down