Lifecycle Policies two index templates

I have two very similar index templates with the same mappings but changes in replications and Lifecycle policies. See templates below, INDEX 1 has "template": "bwlog*" with "order": 5 and a Lifecycle management. INDEX 2 has "template": "bwlog*apache" with order: 10 and no lifecycle management.

The indexes have been working great until I added the lifecycle management to the one temple.
Now both indexes are being created with the lifecycle management associated. The "number_of_replicas" is being applied correctly to the individual indexes at creation.

INDEX 1:
{
"template": "bwlog*",
"order": "5",
"aliases": {
},
"settings": {
"index": {
"number_of_replicas": "1",
"number_of_shards": "60",
"refresh_interval" : "15s"
},
"index.codec": "best_compression",
"index.lifecycle.name": "warm2days_delete10days",
"index.routing.allocation.require.box_type" : "hot"
},
"mappings": {
....

INDEX 2:
{
"template": "bwlogapache",
"order": "10",
"aliases": {
},
"settings": {
"index.routing.allocation.require.box_type": "hot",
"index": {
"number_of_replicas": "1",
"number_of_shards": "1",
"refresh_interval" : "15s"
},
"index.codec": "best_compression"
},
"mappings": {
........

I am guessing this is a hierarchy issue of some sort, can anyone provide some direction?