-
Notifications
You must be signed in to change notification settings - Fork 225
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
SqlAGReplica: Rename parameters PrimaryReplicaSQLServer and PrimaryReplicaSQLInstanceName #922
Labels
breaking change
When used on an issue, the issue has been determined to be a breaking change.
enhancement
The issue is an enhancement request.
Comments
@nabrond @randomnote1 What do you think? |
Yes, I agree these should be updated for consistency. |
johlju
added
breaking change
When used on an issue, the issue has been determined to be a breaking change.
enhancement
The issue is an enhancement request.
help wanted
The issue is up for grabs for anyone in the community.
high priority
The issue or PR should be resolved first. It is of less priority than the label 'Blocking Release'.
and removed
discussion
The issue is a discussion.
labels
Dec 1, 2017
Working on this. |
johlju
added
in progress
The issue is being actively worked on by someone.
and removed
help wanted
The issue is up for grabs for anyone in the community.
labels
Dec 5, 2017
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Dec 5, 2017
- BREAKING CHANGE: Parameters PrimaryReplicaSQLServer and PrimaryReplicaSQLInstanceName has been renamed to PrimaryReplicaServerName and PrimaryReplicaInstanceName respectively (issue dsccommunity#922).
5 tasks
johlju
added a commit
that referenced
this issue
Dec 6, 2017
- Changes to SqlRS - BREAKING CHANGE: Parameters RSSQLServer and RSSQLInstanceName has been renamed to DatabaseServerName and DatabaseInstanceName respectively (issue #923). - Changes to SqlAGReplica - BREAKING CHANGE: Parameters PrimaryReplicaSQLServer and PrimaryReplicaSQLInstanceName has been renamed to PrimaryReplicaServerName and PrimaryReplicaInstanceName respectively (issue #922).
vors
removed
the
high priority
The issue or PR should be resolved first. It is of less priority than the label 'Blocking Release'.
label
Dec 6, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
When used on an issue, the issue has been determined to be a breaking change.
enhancement
The issue is an enhancement request.
Details of the scenario you tried and the problem that is occurring:
The work renaming parameters in issue #308 does not mention the parameters
PrimaryReplicaSQLServer
andPrimaryReplicaSQLInstanceName
in the resource SqlAGReplica.https://github.com/PowerShell/SqlServerDsc/blob/9a1080c4da5d513eb4191388206cf37c16c0a0fd/DSCResources/MSFT_SqlAGReplica/MSFT_SqlAGReplica.schema.mof#L8-L9
I suggest we rename them to
PrimaryReplicaServerName
andPrimaryReplicaInstanceName
respectively.The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
The text was updated successfully, but these errors were encountered: