Skip to content

Manually pin Container instance for v3 #3912

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.

Sign up for GitHub

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

Merged
danielrbradley merged 2 commits into from
Jan 30, 2025
Merged

Manually pin Container instance for v3 #3912

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
362500f
Manually pin Container instance for v3
danielrbradley Jan 30, 2025
997c17e
Merge branch 'master' into pin-v3-container-instance
danielrbradley Jan 30, 2025
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 versions/v3-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,12 @@ ConfidentialLedger:
ConnectedVMwarevSphere:
expectTracking: preview
notes: Only preview versions
ContainerInstance:
exclusions:
NGroup: 2024-11-01-preview
notes: |
Latest version that's live and contains ContainerGroup and ContainerGroupProfile is 2024-05-01-preview so we're manually pinning that for v3.
The NGroup resource doesn't appear in `az provider list`. TODO: review in v4.
ContainerRegistry:
explicit: true
expectAdditions: true
Expand Down
2 changes: 2 additions & 0 deletions versions/v3-spec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

ApiManagement:
tracking: 2022-09-01-preview
ContainerInstance:
tracking: 2024-05-01-preview
ContainerRegistry:
additions:
CredentialSet: 2023-01-01-preview
Expand Down