Skip to content

AIO M2 Spec Updates#30039

Merged
hmmorales merged 50 commits intomainfrom
release/0.7.0-preview
Aug 15, 2024
Merged

AIO M2 Spec Updates#30039
hmmorales merged 50 commits intomainfrom
release/0.7.0-preview

Conversation

@hmmorales
Copy link
Copy Markdown
Member

@hmmorales hmmorales commented Jul 31, 2024

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.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:

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:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    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

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next 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.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in 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.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Jul 31, 2024

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Jul 31, 2024

@hmmorales hmmorales changed the title init PR AIO M2 Spec Updates Aug 6, 2024
nonsocode and others added 2 commits August 13, 2024 15:44
* Audience, SecretRef, TLS

* CloudEventAttributeType

* x509

* update schema

* PR feedback

* schema update

* key as well

* remove MQ disable/enable

* bring back broker

* generate schema

* format

* make props read-only

* remove mq

* schema update

* make togles read write

* schema update

* use mode flags

* new line

* switch to state

* state
@gary-x-li
Copy link
Copy Markdown
Contributor

Please fix the following errors:

❌ Swagger PrettierCheck
❌ Swagger LintDiff
❌ Swagger ModelValidation

hmmorales and others added 3 commits August 13, 2024 17:19
* fix examples

* fix

* typo

* instance examples

* another typo
* remove Service accounts

* update instance defintion

* sync changes
* remove Service accounts

* update instance defintion

* sync changes

* examples

* examples

* update second example

* Instance schema and example update
@bilalsellak
Copy link
Copy Markdown

There are 2 batching types @hmmorales @nonsocode

For fabric, datalake, and dataexplorer:
batching:
latencySeconds: (default of 60)
maxMessages: (default of 100000)

For Kafka:
batching:
latencyMs: (default of 5)
maxBytes: (default of 1000000)
maxMessages: (default of 100000)
mode: (default of Enabled)

Based off of this, and looking at the typespec, it looks correct

* Revert "Model validation pass 4 (#30220)"

This reverts commit d73c5c8.

* ...
@hmmorales
Copy link
Copy Markdown
Member Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 3 pipeline(s).

};

@doc("The properties of the dataflows instance.")
dataflows?: DataFlowInstanceProperties = #{ state: OperationalMode.Enabled };
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

DataFlowInstanceProperties

Should it be DataflowInstanceProperties? You've changed the casing in this PR but there're a couple in this file with an uppercase F.

}

@doc("Kafka endpoint Authentication properties. NOTE - only authentication property is allowed per entry")
model DataFlowEndpointKafkaAuthentication {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

DataFlowEndpointKafkaAuthentication

Dataflow...?

reason: User defined properties that are not subject to any validations.
- suppress: BodyTopLevelProperties
reason: Temporary suppression due to failing pipeline.
- suppress: PatchBodyParametersSchema
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PatchBodyParametersSchema

Can you specify where property here instead of suppressing globally?

* fix: Lowercase d in dataflow

* uncomment supression

* supress path

* schema

* drill down

* stop at identity

* run gen
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Suppression ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. 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.

7 participants