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

Provide support for resource provider profiles #400

Open
Stijnc opened this issue Aug 31, 2020 · 2 comments
Open

Provide support for resource provider profiles #400

Stijnc opened this issue Aug 31, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@Stijnc
Copy link

Stijnc commented Aug 31, 2020

Is your feature request related to a problem? Please describe.

Currently you need to specify the api version for each resource type.
This makes it very cumbersome to maintain and to keep it up to date.

Describe the solution you'd like
A 'provider' resource could append the correct api version to each resource.

Provider resources could follow the concept of profiles in azure stack hub

@ghost ghost added the Needs: Triage 🔍 label Aug 31, 2020
@alex-frankel
Copy link
Collaborator

Is this equivalent to #16?

#364 also seems related

@Stijnc
Copy link
Author

Stijnc commented Aug 31, 2020

As per Brian's comment to #16, I do think so, but I would leverage an already existing concept. As edge/ onpremises can easily be included.

As per #364, it would perfectly relate.

Hypotetical example:

Resource provider azure.profile = {
Name = '2019-03-01-hybrid'
}

resource stg 'Microsoft.Storage/storageAccounts= {
name: 'uniquestorage001' // must be globally unique
location: 'eastus'
kind: 'Storage'
sku: {
name: 'Standard_LRS'
}
}

The api version could easily be append to each resource during build based on the already existing profiles and easily eliminates the micro management need in api profiles.
If a resourced referenced a specific api, it supersedes the defined top level profile.

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