-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
fleet autoupgrade GA - add autoupgradeprofilestatus #32634
base: release-aks-fleet-2025-03-01
Are you sure you want to change the base?
fleet autoupgrade GA - add autoupgradeprofilestatus #32634
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Generated ApiView
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
@@ -2249,6 +2278,36 @@ | |||
}, | |||
"readOnly": true | |||
}, | |||
"AutoUpgradeProfileStatus": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
"type": "object", | ||
"description": "AutoUpgradeProfileStatus is the status of an auto upgrade profile.", | ||
"properties": { | ||
"lastTriggeredAt": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the preference would be to keep the naming as is, as style of existing fleet datatypes with time do not include "InUTC"
"readOnly": true | ||
}, | ||
"lastTriggerError": { | ||
"$ref": "../../../../../../common-types/resource-management/v3/types.json#/definitions/ErrorDetail", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
"description": "The error details of the last trigger.", | ||
"readOnly": true | ||
}, | ||
"lastTriggerUpgradeVersions": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, there will be a large amount / undefined variations of version types
@@ -2212,6 +2237,10 @@ | |||
"disabled": { | |||
"type": "boolean", | |||
"description": "If set to False: the auto upgrade has effect - target managed clusters will be upgraded on schedule.\nIf set to True: the auto upgrade has no effect - no upgrade will be run on the target managed clusters.\nThis is a boolean and not an enum because enabled/disabled are all available states of the auto upgrade profile.\nBy default, this is set to False." | |||
}, | |||
"autoUpgradeProfileStatus": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
Please fill in this too. |
specification/containerservice/Fleet.Management/update/autoupgradeprofile.tsp
Show resolved
Hide resolved
d0e054a
to
0541cf1
Compare
df281e4
to
988b0d3
Compare
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
1 similar comment
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
add tsp files add v5 version generate examples transfer examples try generate oav fix generate transfer examples fix gen fix format run prettier on examples manual fix examples copy examples fix updateid fix subid fix lro header copy run pretty add sub param copy add sub param add sub reset examples reset to release reset examples
193565b
to
b43b9ed
Compare
237e908
to
3bdbac9
Compare
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.