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.

Sign up for GitHub

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

Jump to bottom

consul/connect: trigger update as necessary on connect changes #9029

Merged
merged 1 commit into from
Oct 5, 2020
Merged

consul/connect: trigger update as necessary on connect changes #9029

merged 1 commit into from
Oct 5, 2020

Commits on Oct 5, 2020

  1. consul/connect: trigger update as necessary on connect changes 

    This PR fixes a long standing bug where submitting jobs with changes
to connect services would not trigger updates as expected. Previously,
service blocks were not considered as sources of destructive updates
since they could be synced with consul non-destructively. With Connect,
task group services that have changes to their connect block or to
the service port should be destructive, since the network plumbing of
the alloc is going to need updating.

Fixes #8596 #7991

Non-destructive half in #7192
    @shoenig
    shoenig committed Oct 5, 2020
    Configuration menu
    Copy the full SHA
    37cd0ec View commit details
    Browse the repository at this point in the history