Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v2.5.0 #614

Merged
merged 56 commits into from
Jan 25, 2024
Merged

Release v2.5.0 #614

merged 56 commits into from
Jan 25, 2024

Conversation

jeremmfr
Copy link
Owner

FEATURES:

BUG FIXES:

  • resource/junos_aggregate_route, junos_application, junos_bgp_group, junos_bgp_neighbor, junos_bridge_domain, junos_evpn, junos_firewall_filter, junos_firewall_policer, junos_forwardingoptions_sampling_instance, junos_forwardingoptions_sampling, junos_forwardingoptions_storm_control_profile, junos_generate_route, junos_interface_logical, junos_interface_physical, junos_policyoptions_community, junos_routing_instance, junos_security, junos_security_address_book, junos_security_global_policy, junos_security_ike_gateway, junos_security_ike_policy, junos_security_ipsec_policy, junos_security_ipsec_vpn, junos_security_nat_destination_pool, junos_security_nat_destination, junos_security_nat_source_pool, junos_security_nat_static_rule, junos_security_nat_static, junos_security_policy, junos_security_zone_book_address, junos_security_zone, junos_services_flowmonitoring_v9_template, junos_services_flowmonitoring_vipfix_template, junos_static_route, junos_system_syslog_file, junos_system:
    avoid triggering the conflict errors when Terraform calls the resource config validate function and the value for potential conflict is unknown (can be null afterward) (Fix Feature request: removing Conflict Configuration Error when conflicted variable is set to null #611)

jeremmfr and others added 30 commits January 1, 2024 18:21
change date format
- split constants and structs into dedicated file
- rename some constants and structs
- fix xml.Name on structs
Bumps [github.com/cloudflare/circl](https://github.com/cloudflare/circl) from 1.3.3 to 1.3.7.
- [Release notes](https://github.com/cloudflare/circl/releases)
- [Commits](cloudflare/circl@v1.3.3...v1.3.7)

---
updated-dependencies:
- dependency-name: github.com/cloudflare/circl
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.17.0 to 0.18.0.
- [Commits](golang/crypto@v0.17.0...v0.18.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…m/cloudflare/circl-1.3.7

deps: bump github.com/cloudflare/circl from 1.3.3 to 1.3.7
…g/x/crypto-0.18.0

deps: bump golang.org/x/crypto from 0.17.0 to 0.18.0
with reflection to determine if empty
instead of using switch with cases for each field
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
Fix #611
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
…own value

avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
…unknown value

avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
jeremmfr and others added 26 commits January 16, 2024 20:28
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
…own value

avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
…unknown value

avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
avoid trigger the conflict errors when Terraform call
resource config validate and value for potential conflict
is unknown (can be null afterwards)
use resourceDataReadWithoutArg instead of resourceDataReadFrom0String
add junos_chassis_inventory data-source
avoid triggering the conflict errors with unknown values
Bumps [github.com/hashicorp/terraform-plugin-framework](https://github.com/hashicorp/terraform-plugin-framework) from 1.4.2 to 1.5.0.
- [Release notes](https://github.com/hashicorp/terraform-plugin-framework/releases)
- [Changelog](https://github.com/hashicorp/terraform-plugin-framework/blob/main/CHANGELOG.md)
- [Commits](hashicorp/terraform-plugin-framework@v1.4.2...v1.5.0)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/terraform-plugin-framework
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…m/hashicorp/terraform-plugin-framework-1.5.0

deps: bump github.com/hashicorp/terraform-plugin-framework from 1.4.2 to 1.5.0
@jeremmfr jeremmfr added the release Release MR label Jan 25, 2024
@jeremmfr jeremmfr added this to the v2.5.0 milestone Jan 25, 2024
@jeremmfr jeremmfr self-assigned this Jan 25, 2024
@jeremmfr jeremmfr merged commit 51400e7 into v2 Jan 25, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Release MR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant