-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Release v2.5.0 #614
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FEATURES:
BUG FIXES:
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)