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

Renamed replication_schedule to replication_frequence on Azure NetApp Files volume data source #11530

Merged
merged 2 commits into from
Apr 29, 2021

Conversation

paulomarquesc
Copy link
Contributor

Fixes bug #11292, where the data source resource didn't match the correct name.

@ghost ghost added the size/XS label Apr 29, 2021
@paulomarquesc paulomarquesc changed the title Renamed replication_schedule to replication_frequence on data source Renamed replication_schedule to replication_frequence on volume data source Apr 29, 2021
@paulomarquesc paulomarquesc changed the title Renamed replication_schedule to replication_frequence on volume data source Renamed replication_schedule to replication_frequence on Azure NetApp Files volume data source Apr 29, 2021
Copy link
Member

@manicminer manicminer left a comment

Choose a reason for hiding this comment

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

Hi @paulomarquesc, thanks for this bugfix! I've pushed a documentation fix to add the missing attributes and this LGTM 👍

@manicminer manicminer merged commit 96db3f1 into hashicorp:master Apr 29, 2021
manicminer added a commit that referenced this pull request Apr 29, 2021
@ghost
Copy link

ghost commented Apr 30, 2021

This has been released in version 2.57.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.57.0"
}
# ... other configuration ...

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants