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

Don't autoname azure.role.Assignment #127

Merged
merged 1 commit into from
Oct 2, 2018
Merged

Don't autoname azure.role.Assignment #127

merged 1 commit into from
Oct 2, 2018

Conversation

lukehoban
Copy link
Contributor

@lukehoban lukehoban commented Oct 1, 2018

This resource is autonamed to a GUID in the underlying provider - which is the only allowed value - and so should not be autonamed in the Pulumi layer.

Also fixed capitalization from assignment to Assignment - this is a breaking change.

@lukehoban lukehoban added impact/breaking Fixing this issue will require a breaking change impact/changelog labels Oct 1, 2018
@lukehoban lukehoban requested a review from pgavlin October 1, 2018 20:14
resources.go Outdated
@@ -209,7 +209,13 @@ func Provider() tfbridge.ProviderInfo {
"azurerm_autoscale_setting": {Tok: azureResource(azureAutoscale, "Setting")},

// Authorization
"azurerm_role_assignment": {Tok: azureResource(azureRole, "assignment")},
"azurerm_role_assignment": {
Tok: azureResource(azureRole, "assignment"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be Assignment?

This resource is autonamed to a GUID in the underlying provider - which is the only allowed value - and so should not be autonamed in the Pulumi layer.
@lukehoban lukehoban merged commit e934631 into master Oct 2, 2018
@pulumi-bot pulumi-bot deleted the lukehoban/121 branch October 2, 2018 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/breaking Fixing this issue will require a breaking change impact/changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants