-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Added preliminary Rust binding to a whole lot of tspconfig.yaml files #38890
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
base: main
Are you sure you want to change the base?
Added preliminary Rust binding to a whole lot of tspconfig.yaml files #38890
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
...appconfiguration/resource-manager/Microsoft.AppConfiguration/AppConfiguration/tspconfig.yaml
Outdated
Show resolved
Hide resolved
...appconfiguration/resource-manager/Microsoft.AppConfiguration/AppConfiguration/tspconfig.yaml
Outdated
Show resolved
Hide resolved
|
@LarryOsterman: You may want to add validation for the rust config here, alongside the validation for the other languages: |
I was thinking about that, but I believe that @heaths has that on his plate. More importantly, I know for certain that the Rust emitter cannot handle many of these crates (it failed 3 out of 5 tries earlier this week). So adding validation right now is likely to be premature. |
|
Yeah, in the new year. I'm first going to go through and try to generate a Rust crate for every |
Btw, looking at the validation, some of these can be done now (for instance, validating the output location is valid, validating that management plane SDKs have |
SDK configuration pull request
Purpose of this PR
Add Rust bindings to a significant number of tspconfig.yaml files. Note that these bindings do NOT imply that Rust clients will be generated for these packages, neither does it imply that the namespaces for these packages is correct.
Before the decision is made to generate a Rust SDK, please confirm with the architecture board that the package name is correct as is the working directory for the generated package.
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:
tspconfig.yamltemplates:Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.