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

Support configuring vault version handling. #1646

Merged
merged 4 commits into from
Oct 26, 2022

Conversation

benashz
Copy link
Contributor

@benashz benashz commented Oct 26, 2022

Add two new provider fields for configuring way that the provider determines the target Vault server's version.

  • vault_version_override: will set the vault version explicitly, no API requests will be made to retrieve the version
  • skip_get_vault_version: enable to disable API version requests.

If no version can be determined, the lowest supported versioned API semantics will be applied to all resources.

Closes #1643

Add two new provider fields for configuring way that the provider
determines the target Vault server's version.

- vault_version_override: will set the vault version explicitly, no API
  requests will be made to retrieve the version
- skip_get_vault_version: enable to disable API version requests.

If no version can be determined, the lowest supported versioned API
semantics will be applied to all resources.
@benashz benashz added this to the 3.10.0 milestone Oct 26, 2022
Copy link
Contributor

@vinay-gopalan vinay-gopalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Saw 1 potential change, but looks good otherwise

Optional: true,
Default: false,
Description: "Skip the dynamic fetching of the Vault server version.",
ValidateDiagFunc: provider.ValidateDiagSemVer,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be validating a semantic version since this is a boolean?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, good catch! Fixed with 8e28053

@benashz benashz merged commit b3777eb into main Oct 26, 2022
@benashz benashz deleted the VAULT-9495/add-vault-server-version-override branch October 26, 2022 20:50
marcboudreau pushed a commit to marcboudreau/terraform-provider-vault that referenced this pull request Nov 6, 2022
Add two new provider fields for configuring way that the provider
determines the target Vault server's version.

- vault_version_override: will set the vault version explicitly, no API
  requests will be made to retrieve the version
- skip_get_vault_version: enable to disable API version requests.

If no version can be determined, the lowest supported versioned API
semantics will be applied to all resources.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature: Set vaultVersion in ProviderMeta without api call
2 participants