-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: add data presence check for solution history #90
base: master
Are you sure you want to change the base?
Conversation
@@ -313,6 +315,72 @@ public TResponse Execute<TResponse>(OrganizationRequest request, string username | |||
return (TResponse)this.Execute(request); | |||
} | |||
|
|||
/// <inheritdoc/> | |||
public bool HasStartedSolutionHistoryRecords(ILogger logger) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The naming of this method doesn't seem to match what it is actually doing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ewingjm refactored extended service method to better reflect its intent
new ConditionExpression(Constants.SolutionHistory.Fields.Status, ConditionOperator.Equal, Constants.SolutionHistory.Statuses.Started), | ||
}, | ||
}, | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QueryByAttribute
would be more concise here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ewingjm replaced QueryExpression
with QueryByAttribute
src/Capgemini.PowerApps.PackageDeployerTemplate/Adapters/CrmServiceAdapter.cs
Show resolved
Hide resolved
…tion history records
- update existing tests to use the execute multiple solution history mock
- refactor implementation to track original request indexes mapping to ensure returned responses are in the correct order index
- change path to include solution sub-directory to contain the managed solution
Purpose
This change introduces a wait and retry policy when setting the state of processes during solution deployment.
Approach
Introducing a wait and retry policy ensures that all active solution history records are completed before proceeding with the next deployment operations.
TODOs