Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Fix external name configurations of storage_container and storage_blob resources #135

Merged

Conversation

sergenyalcin
Copy link
Collaborator

Description of your changes

Fixes #129

This PR resolves the configuration issues for the two resources.

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

The external resources were provisioned by using the example manifests. Also the update and delete operations were tested.

@sergenyalcin sergenyalcin requested a review from ulucinar January 28, 2022 14:12
@sergenyalcin sergenyalcin self-assigned this Jan 28, 2022
@sergenyalcin sergenyalcin changed the title Fix external name configurations of storage_container and storage_blob resources Fix external name configurations of storage_container and storage_blob resources Jan 28, 2022
Copy link
Collaborator

@ulucinar ulucinar left a comment

Choose a reason for hiding this comment

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

Thank you @sergenyalcin.

return strings.TrimPrefix(idStr, "https://"), nil
}
// https://storacc.blob.core.windows.net/container/blob.vhd
r.ExternalName.GetExternalNameFn = common.GetResourceNameFromIDURLFn(1)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

azurerm_storage_container has wrong external-name in composition after creation
2 participants