You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Hi,
Some of the features that I want to implement are available in the latest providers only, for example:
source = "hashicorp/azuread"
version = "2.28.1"
however the current CAF module is using 2 years old provider for hashicorp/azuread.
source = "hashicorp/azuread"
version = "1.4.0"
While I understand that upgrading them would have a major impact and backward compatibility has to be tested but if CAF has to be adopted enterprise wide, there is an expectation of predictable release/upgrade cycle for these providers.
Questions:
1 - When writing a new feature / bug fix, should we use the latest provider available at hashicorp or the providers defined in main.tf?
2 - What providers versions should be used when writing caf_solution addons?
3 - Within a given CAF Module, do we use any other provider other than or this can also be moved to main.tf:
source = "aztfmod/azurecaf"
Is there a dependency between providers used in CAF_Landingzone & CAF_Solution and terraform-azurerm-caf?
Is there a matrix of versions for terraform-azurerm-caf vs caf_solution/launchpad vs rover? especially when one wants to write a new module or a new addon?
It would be good if we have these answered and added to the Contributions.md as well please.
Thanks
New or Affected Resource(s
azuread_application
Potential Configuration file
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Description
Hi,
Some of the features that I want to implement are available in the latest providers only, for example:
however the current CAF module is using 2 years old provider for hashicorp/azuread.
While I understand that upgrading them would have a major impact and backward compatibility has to be tested but if CAF has to be adopted enterprise wide, there is an expectation of predictable release/upgrade cycle for these providers.
Questions:
1 - When writing a new feature / bug fix, should we use the latest provider available at hashicorp or the providers defined in main.tf?
2 - What providers versions should be used when writing caf_solution addons?
3 - Within a given CAF Module, do we use any other provider other than or this can also be moved to main.tf:
It would be good if we have these answered and added to the Contributions.md as well please.
Thanks
New or Affected Resource(s
azuread_application
Potential Configuration file
No response
References
No response
The text was updated successfully, but these errors were encountered: