I can't believe I'm saying this, but past Mike left things a little confusing - rather than assigning out a range of 20-29 for one year's APIs, and 30-39 for the next, it appears that I had to do some mad juggling that left it in a state where:
2018 APIs occupy the following priorities: 20, 21, 25, 26, 30, 31, 35, 36, 40, 41
2017 API occupy 50-59
Notes in that doc indicate that civic-2018-service must remain higher in the list than the related APIs (though I don't recall why, since they're not sharing an FQDN).
This documents the current allocation of Listener priorities for existing ALB targets: https://github.com/hackoregon/civic-devops/blob/master/docs/HOWTO-track-required-Services-Settings.md
I can't believe I'm saying this, but past Mike left things a little confusing - rather than assigning out a range of 20-29 for one year's APIs, and 30-39 for the next, it appears that I had to do some mad juggling that left it in a state where:
Notes in that doc indicate that civic-2018-service must remain higher in the list than the related APIs (though I don't recall why, since they're not sharing an FQDN).
So I propose the following changes: