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

Is there a plan to make Microsoft Graph objects standard and not require experimental features enablement? #152

Open
masonwolff opened this issue Jul 9, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@masonwolff
Copy link

Is your feature request related to a problem? Please describe.
I am wondering if there is a plan to remove the need for the experimental features configuration that is required to access the "microsoftGraph" provider?

@masonwolff masonwolff added the enhancement New feature or request label Jul 9, 2024
@dkershaw10 dkershaw10 self-assigned this Jul 10, 2024
@dkershaw10
Copy link
Collaborator

dkershaw10 commented Jul 10, 2024

Not sure if you are asking two questions here @masonwolff?

  1. Remove the need to specify the experimental feature config to use the microsoftGraph provider?
  2. Remove the need to even specify the provider or extension statement (extension to be added in the upcoming v0.29 Bicep release - see [Bicep Extensibility] Deprecating the term provider in favor of extension Azure/bicep#14374)?

For 1: yes, we plan to remove this requirement, once the Bicep "extensibility" feature comes out of preview.
For 2: we have discussed whether this statement is required or not, if the resource declarations already have the Microsoft.Graph namespace. I think this one is still TBD, and the provider/extension statement is still required for now.

@dkershaw10
Copy link
Collaborator

@masonwolff Have I answered your question? If so, please go ahead and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants