Update kubernetesConfiguration.fluxConfiguration resource version to 2024-11-01

[arnaud-tincelin]

Add support for kubernetesConfiguration.fluxConfiguration resource to version to 2024-11-01 so that it supports the spec.gitRepository.provider property.

Notes: to generate the code I ran the task cmd but it also updated other resources about ACR. Is this something normal?
I did not write documentation nor tests, did I miss something?

We need this feature ASAP for a customer delivery. Do you have an estimated date for the next ASO release?

• [] this PR contains documentation
• this PR contains tests
• this PR contains YAML Samples

[matthchr]

Notes: to generate the code I ran the task cmd but it also updated other resources about ACR. Is this something normal?

You've updated the submodule, which brings with it changes upstream that teams have made to their specs. Usually this is just docs but every once in a while there are actual structural changes to existing API versions (almost always because the published spec actually was wrong and didn't work)

I did not write documentation nor tests, did I miss something?

Docs will be automatic. Tests you'll have to add (see my comments)

[theunrepentantgeek]

Thanks for the PR, much appreciated.

We need this feature ASAP for a customer delivery. Do you have an estimated date for the next ASO release?

We're targeting mid-April for the release of ASO v2.13, which isn't far off.

Also, as soon as your PR merges, we'll automatically publish a new experimental release which you can immediately use for testing.

[theunrepentantgeek]

The changes under v2/api/machinelearningservices are technically breaking, but they originate upstream.

To simplify things for you, I've pulled out the submodule update into PR #4640 so these changes don't pollute your PR. Once that's merged, you'll need to update your branch.

[theunrepentantgeek]

A couple of minor tweaks, including a missing recording of the sample, but otherwise looks great.

Thanks for your contribution. We're looking forward to merging this.

We need to first merge PR #4640 as a cleanup, then we should be clear to merge this one once CI passes.

[theunrepentantgeek]

Renaming this test is the right thing to do - but you'll need to rerecord the test. This is failing in CI with this error:

=== RUN   Test_KubernetesConfiguration_FluxConfiguration_20230501_CRUD
=== PAUSE Test_KubernetesConfiguration_FluxConfiguration_20230501_CRUD
=== CONT  Test_KubernetesConfiguration_FluxConfiguration_20230501_CRUD
    kube_per_test_context.go:167: creating recorder: required environment variable "AZURE_SUBSCRIPTION_ID" was not supplied
--- FAIL: Test_KubernetesConfiguration_FluxConfiguration_20230501_CRUD (0.00s)

This error appears when there's no recording for the test.

Some background: The test recording is named for the test (so the old test recording is Test_KubernetesConfiguration_FluxConfiguration_CRUD.yaml). But, the name of the test is also used to seed a random number generator that's used to generate unique names within the test, so it can't simply be renamed.

Delete the old file and create a new recording.

[arnaud-tincelin]

I renamed Test_KubernetesConfiguration_FluxConfiguration_CRUD to Test_KubernetesConfiguration_FluxConfiguration_20230501_CRUD and updated the test as it was failing on my side (the flux extension was never installed on the cluster).

I remade several tests (see the commit content)

[theunrepentantgeek]

Looks like we're at the whack-a-mole stage of getting this merged. 😢

There's another merge conflict, this one for the submodule at v2/specs/azure-rest-api-specs.

Easiest fix is probably to git merge main into your branch.

[theunrepentantgeek]

/ok-to-test sha=059f5d3