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

Update the production connection status on publication #240

Merged
merged 1 commit into from
Feb 21, 2019

Conversation

MKodde
Copy link
Contributor

@MKodde MKodde commented Feb 21, 2019

The status was not updated on the Service entity, The first time when
the status is not yet set to either requested or active, the status
is updated.

https://www.pivotaltracker.com/story/show/163732191

@pablothedude
Copy link
Contributor

I think a test should be a valuable addition. Also we should maybe look into a state engine of some sort later on to keep the PublishEntity*CommandHandlers maintainable. The latter is a suggestion we could very well address later on.

The status was not updated on the Service entity, The first time when
the status is not yet set to either requested or active, the status
is updated.

https://www.pivotaltracker.com/story/show/163732191
@MKodde MKodde force-pushed the feature/update-service-status-on-entity-publication branch from e85a6a2 to fa86eba Compare February 21, 2019 16:42
@MKodde
Copy link
Contributor Author

MKodde commented Feb 21, 2019

Yes, some handlers are growing and growing. I'm putting a todo on my list to create a TD ticket for this.

I also fixed the test.

@MKodde MKodde merged commit dcac7ae into develop Feb 21, 2019
@MKodde MKodde deleted the feature/update-service-status-on-entity-publication branch August 28, 2019 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants