-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update services before starting #559
base: refactor/multi-chain-support-frontend
Are you sure you want to change the base?
Update services before starting #559
Conversation
try { | ||
const serviceToStart = service ?? middlewareServiceResponse; | ||
await ServicesService.startService(serviceToStart!.service_config_id); | ||
if (service && !createServiceResponse) { |
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.
does create also run the service now? so we shouldn't start manually?
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.
good catch thanks, should be the other way round i think 😓
// Update if service already exists and template hash has changed | ||
if (!createServiceResponse && service) { | ||
try { | ||
if (service.hash !== serviceTemplate.hash) { |
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.
is this needed to support previous versions?
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.
correct, there were issues when users migrated from legacy staging to the latest; the template hashes had updated but did not support the new environment
Proposed changes
Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that apply