- 
                Notifications
    You must be signed in to change notification settings 
- Fork 260
Adds support for custom ServiceConfig settings for extensions #6013
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
Conversation
        
          
                cli/azd/extensions/azure.ai.agents/internal/project/service_target_agent.go
          
            Show resolved
            Hide resolved
        
      8eb2e4f    to
    85bb033      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am worried about who's responsible for writing the service-config....
Is it the extension init command?
Is it a template-owner who knows about this config?
Is it the end-user who needs to know where to find and update this config?
Part of me feels like extensions should not have write access to azure.yaml (only read)... and if azd should protect the project somehow.
| 
 The extension author will be required to maintain and support the  Right now part of the  
 Would love to know more about this and why we should limit write access? | 
| /check-enforcer override | 
85bb033    to
    ab915ef      
    Compare
  
    | Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
 bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
 MSI
 Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference | 
Add Config Field Support to ServiceConfig Mappers
Overview
This PR adds support for the new
Configfield inazdext.ServiceConfig, enabling service targets to use custom configuration while maintaining backward compatibility.Benefits
This enhancement supports the broader extensibility framework allowing
azdextensions to provide custom service targets with their own configuration requirements.Example
azure.yaml