0.1.24

NSOF-6327 resources: don't raise error in case a resource was not found

This way those resources will simply be removed from state in the read function and be recreated in the next apply execution
This is done per customer request https://github.com/nsofnetworks/terraform-provider-pfptmeta/issues/30 and it's a common standard in the terraform provider plugins (AWS and GCP and probably more)

0.1.23

NSOF-6320 network_elements: don't send 'enable' flag when writing map…

0.1.21

NSOF-5927 device-settings: use GetOkExists for bool attr of device se…

0.1.20

NSOF-5982 metaport_cluster: support data-source name param

Even though name is not unique for metaport clusters - costumer's feedback
brought the need to onboard metaports and metaport clusters outside of tf code and later - use
the metaport name to find it and attach mapped elements to it from
terraform.

Because it's not unique - in case there is more then one metaport cluster with the
specified name - an error will be returned.

Customer's ticket: https://github.com/nsofnetworks/terraform-provider-pfptmeta/issues/11

0.1.19

NSOF-5770 roles: enforce at least one of 'apply_to_orgs', 'all_suborg…

0.1.18

NSOF-5652 doc: add newline between notes

0.1.17

NSOF-5931 log_streaming_access_bridge: use pagerDuty notification cha…

0.1.16

NSOF-5929 trusted_network: make 'criteria' optional instead of 'Requi…

0.1.15

NSOF-5926 access_control: allow empty 'allowed_routes' list

0.1.14

NSOF-5931 log_streaming_access_bridge: introduce resource and data-so…