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

Update pipeline task release notes v7.0.0 and v6.4.0 #836

Merged
Show file tree
Hide file tree
Changes from 5 commits
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
6 changes: 6 additions & 0 deletions releaseNotes/AzureDevOpsPipelineExtension.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,12 @@ The Azure App Configuration extension in Azure DevOps pipeline has been publishe

![sample](pictures/AzureDevOpsExtensionVersionSample.PNG)

### v7.0.0 - November, 20 2023
**Breaking changes**
- Updated to fail the task if any Key Vault references cannot be resolved or if the resolved values are invalid to be set as the pipeline secret.
Copy link
Member

Choose a reason for hiding this comment

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

Ideally when we call out a breaking change, we inform how to work around it. In this case the user needs to enable the option to treat key vault errors as warnings.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good point. I have also added more information on a workaround, let me know if thats okay


* Added an option to treat Key Vault resolution errors as warnings.
Copy link
Member

Choose a reason for hiding this comment

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

It doesn't seem like the new option we've added is a breaking change. In that case it should be under a different header than "Breaking changes"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have added another header Enhancement let me know if thats okay


### v6.5.0 - October, 13 2023
* Added capability to use workload identity federation for authentication.

Expand Down
3 changes: 3 additions & 0 deletions releaseNotes/AzureDevOpsPushPipelineExtension.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
Azure App Configuration Push extension for Azure DevOps pipeline can be installed from the [Azure DevOps marketplace](https://marketplace.visualstudio.com/items?itemName=AzureAppConfiguration.azure-app-configuration-task-push). The version information can be found in the console when the task is executed:
![sample](pictures/AzureDevOpsPushExtensionVersionSample.PNG)

### v6.4.0 - November, 20 2023
* Added support for a feature that allows users to add a prefix to the key name of feature flags. This will provide more flexibility and better organization of feature flags for users.[#810](https://github.com/Azure/AppConfiguration/issues/810).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
* Added support for a feature that allows users to add a prefix to the key name of feature flags. This will provide more flexibility and better organization of feature flags for users.[#810](https://github.com/Azure/AppConfiguration/issues/810).
* Added support for a feature that allows users to add a prefix to the key name of feature flags. This will provide more flexibility and better organization of feature flags. [#810](https://github.com/Azure/AppConfiguration/issues/810).


### v6.3.0 - October, 13 2023
* Added capability to use workload identity federation for authentication.

Expand Down