Upgrading to 0.6.19
Check these against what you run:
- A connection property that starts with a secret scheme and a colon.
env:,secret:,vault:,aws-secrets:,azure-kv:andgcp-secret:now mean a reference in the properties listed below, so a Kafka broker calledvaultwrittenbootstrap.servers: vault:9092, or a queue calledenv:orders, now fails to resolve and stops the channel. Write such a value through a default:${BROKER:vault:9092}. Other text with a colon, such askafka:9092, is unaffected. - A
${NAME}that 0.6.18 refused. It now resolves, so the channel starts. Before 0.6.18 such a value was used as a literal name, so if you move a Kafkagroup.idfrom a literal${NAME}to a resolved one, it is a new consumer group and starts fromauto.offset.reset(defaultearliest), not from the old group’s offsets. RAW_BODY_UNMASKEDandRAW_BODY_STOREDwarn in more places. They now also fire on a flow that reads a store a masking flow wrote raw text to. These are warnings, andRAW_BODY_UNMASKEDbecomes an error in a later release.
There is no migration, archive format, deploymentId or snapshot format change.