Skip to content

AIO 2507 preview #33810

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

Open
wants to merge 166 commits into
base: main
Choose a base branch
from
Open

Conversation

nonsocode
Copy link
Member

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

Copy link

openapi-pipeline-app bot commented Apr 8, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
    When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
    Automation should then add WaitForARMFeedback label.
    ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

Copy link

openapi-pipeline-app bot commented Apr 8, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

Copy link

github-actions bot commented Apr 8, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.IoTOperations
TypeSpec Microsoft.IoTOperations

@AzureRestAPISpecReview AzureRestAPISpecReview added the BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required label May 13, 2025
@nonsocode nonsocode marked this pull request as ready for review May 14, 2025 16:05
@AzureRestAPISpecReview AzureRestAPISpecReview added ARMReview new-api-version NotReadyForARMReview ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test labels May 14, 2025
@JeffreyRichter JeffreyRichter added the BreakingChange-Approved-UserImpact Changes are not backward compatible and may cause customer disruption. label May 14, 2025
@AzureRestAPISpecReview AzureRestAPISpecReview added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed NotReadyForARMReview labels May 14, 2025
@TimLovellSmith
Copy link
Member

Can you please fix the PR description

@TimLovellSmith TimLovellSmith added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label May 14, 2025
@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 14, 2025
{
"endpointType": "chkkpymxhp",
"version": "chkkpymxhp",
"configurationSchemaRefs": {
Copy link
Member

Choose a reason for hiding this comment

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

why call it configurationSchemaRefs instead of just configurationSchemas?

Copy link
Member Author

Choose a reason for hiding this comment

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

@abhipsaMisra Would it make more sense to call this configurationSchema? all contained properties have ref in their name

"resource": {
"properties": {
"aioMetadata": {
"aioMinVersion": "tkiz",
Copy link
Member

Choose a reason for hiding this comment

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

more realistic values would make for better docs right

Copy link
Member Author

@nonsocode nonsocode May 14, 2025

Choose a reason for hiding this comment

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

Yes they will be better. I'll update with real examples

registrySettingsType: RegistryEndpointRef;

/** The name of the registry endpoint. */
registryEndpointRef: string;
Copy link
Member

Choose a reason for hiding this comment

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

I wonder why call it a registeryEndpointRef and not just registryEndpoint? Why is it a 'name of'? In what sense is the name going to be dereferenced?

Copy link
Member Author

Choose a reason for hiding this comment

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

ref is a convention we use when making reference to kubernetes resource names.

@added(Versions.`2025-07-01-preview`)
model AkriConnectorsSecret {
/** The key in the secret to be mounted. */
secretKey: string;
Copy link
Member

@TimLovellSmith TimLovellSmith May 14, 2025

Choose a reason for hiding this comment

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

Wondering: does this need to be annotated as @secret or something? So that its x-ms-secret in the open api spec?

Is this a secret value as I'm imagining?

Copy link
Member Author

Choose a reason for hiding this comment

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

No, this isn't a secret in that sense. This is a property in a kubernetes secret. It's akin to the name of an azure secret in a keyvault


@doc("X509 Certificate Authentication properties.")
model X509ManualCertificate {
@doc("Kubernetes secret containing an X.509 client certificate. This is a reference to the secret through an identifying name, not the secret itself.")
Copy link
Member

Choose a reason for hiding this comment

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

a secret where?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is a kubernetes secret name. This is not the secret content.

@@ -19,6 +19,10 @@ words:
- mqtt
- otlp
- populator
- azurecr
Copy link
Member

Choose a reason for hiding this comment

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

considered using less abbreviated 'azure container registry' or other stylings azureCR or azure_cr instead?

@@ -54,10 +53,25 @@ model InstanceProperties {
@doc("The reference to the Schema Registry for this AIO Instance.")
schemaRegistryRef: SchemaRegistryRef;

@doc("The reference to the AIO Secret provider class.")
@added(Versions.`2025-07-01-preview`)
defaultSecretProviderClassRef?: SecretProviderClassRef;
Copy link
Member

Choose a reason for hiding this comment

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

Putting 'classRef' in the name seems quite confusing to me.
What's easier to understand. "I configure my default secret provider", or "I configure my default secret provider class ref"?
Is the distinction really something that matters to customers?


@doc("The Azure Device Registry Namespace used by Assets, Discovered Assets and devices")
@added(Versions.`2025-07-01-preview`)
adrNamespaceRef?: AzureDeviceRegistryNamespaceRef;
Copy link
Member

Choose a reason for hiding this comment

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

more naming comments: why not call it an 'azureDeviceRegistryNamespace'?

[aside: generally these naming comments are optional to address... opinion based feedback, right, ymmv]

@added(Versions.`2025-07-01-preview`)
model DataflowGraphDestinationNodeSettings {
/** The endpoint reference for the destination. */
endpointRef: string;
Copy link
Member

Choose a reason for hiding this comment

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

Could perhaps use a fuller documentation of how it is an 'endpointRef' as opposed to an endpoint (or uri??).

@@ -39,6 +39,10 @@ model DataflowProperties {
@doc("Mode for Dataflow. Optional; defaults to Enabled.")
mode?: OperationalMode = Enabled;

@doc("Disk persistence mode.")
@added(Versions.`2025-07-01-preview`)
requestDiskPersistence?: OperationalMode;

Choose a reason for hiding this comment

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

thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review ARMReview BreakingChange-Approved-UserImpact Changes are not backward compatible and may cause customer disruption. BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required new-api-version ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager RPaaS SuppressionReviewRequired TypeSpec Authored with TypeSpec
Projects
None yet
Development

Successfully merging this pull request may close these issues.