chore(deps): update dependency azure/azure-service-operator to v2.11.0 #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.9.0
->v2.11.0
Release Notes
Azure/azure-service-operator (Azure/azure-service-operator)
v2.11.0
Compare Source
Release notes
Breaking changes
Moved all the "ARM" variants of the CRD types into dedicated subpackages
This is only breaking for consumers of the Go package, not for users of the YAML, and only for those using the ARM types directly.
Upcoming Breaking changes
Deprecated managedclusters.containerservice.azure.com API versions
We recommend you move to use a different CRD version to avoid errors.
For more details see the breaking changes document.
New resources
Features
Improvements
Bug fixes
asoctl clean crds
(#4403)Documentation
Full Changelog: Azure/azure-service-operator@v2.10.0...v2.11.0
v2.10.0
Compare Source
Release notes
Breaking changes
MachineLearningServices/WorkspacesCompute properties marked as a SecretReference
The below properties on
WorkspacesCompute
has been changed from a string to aSecretReference
We always try to avoid breaking changes, but in this case, allowing raw passwords in the spec is a security problem and as such we've
decided to make a break to correct this issue.
Affected Properties:
For more details see the breaking changes document.
Upcoming Breaking changes
We've made a number of breaking changes to properties to ensure they correctly use Secrets to store secret values.
To reduce the likelihood of future breaking changes of this type, we are working to improve our automated detection of properties that should be treated as secrets, see PR #4289.
New resources
Features
Improvements
export template
command (#4245)Bug fixes
Documentation
Full Changelog: Azure/azure-service-operator@v2.9.0...v2.10.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.