Skip to content
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

Differentiate SDK Generation Results for Disabled or Unconfigured SDK Generation #9860

Open
raych1 opened this issue Feb 18, 2025 · 0 comments
Assignees
Labels
Automation Tool Central-EngSys This issue is owned by the Engineering System team.

Comments

@raych1
Copy link
Member

raych1 commented Feb 18, 2025

Currently, the result will be set as 'failed' when the SDK configuration is not enabled in the spec configuration files, tspconfig.yaml or readme.md.

We would like to separate these configuration issues from the real failures.

@raych1 raych1 converted this from a draft issue Feb 18, 2025
@raych1 raych1 self-assigned this Feb 18, 2025
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 18, 2025
@raych1 raych1 added Automation Tool and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Feb 18, 2025
@raych1 raych1 changed the title Differentiate the SDK generation result when the configuration is not enabled Differentiate SDK Generation Results for Disabled or Unconfigured SDK Generation Feb 18, 2025
@raych1 raych1 moved this from Backlog to In Progress in API to SDK automation Feb 18, 2025
@raych1 raych1 added the Central-EngSys This issue is owned by the Engineering System team. label Feb 18, 2025
@raych1 raych1 moved this from 🤔 Triage to 🐝 Dev in Azure SDK EngSys 🤖🧠 Feb 18, 2025
@kurtzeborn kurtzeborn moved this from 🐝 Dev to 🎊 Closed in Azure SDK EngSys 🤖🧠 Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Automation Tool Central-EngSys This issue is owned by the Engineering System team.
Projects
Status: In Progress
Status: 🎊 Closed
Development

No branches or pull requests

1 participant