Parameter Context under version control

[ta...@belastingdienst.nl]

When I change the Parameter Context of a PG under version control, this is
not noted as a change (for the version control system).
When I change something else on the same panel (for example the
back-pressure) it is noted as a change, as expected.

Is this behaviour "as-designed" ?


Kind regards / Met vriendelijke groet,

Tiemen Fiat

------------------------------------------------------------------------
De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten.
Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren.

The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email.
This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.

RE: Parameter Context under version control

[Isha Lamboo <is...@virtualsciences.nl>]

Hi Tiemen,

Parameter contexts and their interaction with the versioning systems are sometimes a bit counterintuitive. The context a PG links to is included in the versioned flow definition and it will be created on the destination NiFi when imported if it doesn’t exist yet. If the destination context already exists it will add new properties, but not update existing ones, since they are supposed to be different per environment. Parameter contexts are not part of a PG, but kind of piggyback ride on them in the versioning system.

Since you didn’t change the PG itself but only the linked context, no change is marked. If it had been, all the other PGs that are linked to the same parameter context to also show as changed. That would make you lose track of real changes much quicker. So yes, you need to make another change to activate the menu option to commit a new version and it will include the new values in the definition then.

Regards/Groeten,

Isha

Van: ta.fiat@belastingdienst.nl <ta...@belastingdienst.nl>
Verzonden: maandag 4 juli 2022 13:17
Aan: users <us...@nifi.apache.org>
Onderwerp: Parameter Context under version control


When I change the Parameter Context of a PG under version control, this is not noted as a change (for the version control system).
When I change something else on the same panel (for example the back-pressure) it is noted as a change, as expected.

Is this behaviour "as-designed" ?
Kind regards / Met vriendelijke groet,

Tiemen Fiat

------------------------------------------------------------------------
De Belastingdienst stelt e-mail niet open voor aanvragen, aangiften, bezwaarschriften, verzoeken, klachten, ingebrekestellingen en soortgelijke formele berichten.
Dit bericht is uitsluitend bestemd voor de geadresseerde. Het bericht kan vertrouwelijke informatie bevatten waarvoor de fiscale geheimhoudingsplicht geldt. Als u dit bericht per abuis hebt ontvangen, wordt u verzocht het te verwijderen en de afzender te informeren.

The Dutch Tax and Customs Administration does not accept filings, requests, appeals, complaints, notices of default or similar formal notices, sent by email.
This message is solely intended for the addressee. It may contain information that is confidential and legally privileged. If you are not the intended recipient please delete this message and notify the sender.