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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

r/database_secret_backend_configuration - elasticsearch missing fields #1300

Merged
merged 6 commits into from Apr 20, 2022

Conversation

DrFaust92
Copy link
Contributor

Community Note

  • Please vote on this pull request by adding a 馃憤 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Release note for CHANGELOG:

resource/database_secret_backend_configuration - add missing elasticseach fields

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccDatabaseSecretBackendConnection_elasticsearch'

--- PASS: TestAccDatabaseSecretBackendConnection_elasticsearch (27.07s)

@DrFaust92 DrFaust92 changed the title r/database_secret_backend_configuration - elasticseach missing fields r/database_secret_backend_configuration - elasticserach missing fields Jan 16, 2022
@DrFaust92 DrFaust92 changed the title r/database_secret_backend_configuration - elasticserach missing fields r/database_secret_backend_configuration - elasticsearch missing fields Jan 16, 2022
@DrFaust92
Copy link
Contributor Author

@benashz, I have a feeling Import is broken after the plugin name refactor.

Im getting

Error: no supported database engines configured


    resource_database_secret_backend_connection_test.go:703: Step 2/2 error running import: exit status 1
        
        Error: no supported database engines configured

Ive removed the import check for now but i think that

	db, err := getDBEngine(d)
	if err != nil {
		return err
	}

needs to be moved after the the the actual read calls as on import you only have the id of the resource available.

@benashz
Copy link
Contributor

benashz commented Feb 14, 2022

Thanks @DrFaust92. Good catch. We will address this before the upcoming 3.3.0 release.

@benashz
Copy link
Contributor

benashz commented Feb 15, 2022

@DrFaust92 currently all import tests are passing. Is the error specific to this PR?

@benashz
Copy link
Contributor

benashz commented Feb 15, 2022

@DrFaust92 Actually scratch that. I can reproduce it now.

@DrFaust92
Copy link
Contributor Author

@benashz, LMK if you need any help with that :D

@benashz
Copy link
Contributor

benashz commented Feb 16, 2022

Thanks @DrFaust92 , I have a PR here #1348

@hashicorp-cla
Copy link

hashicorp-cla commented Mar 12, 2022

CLA assistant check
All committers have signed the CLA.

@DrFaust92
Copy link
Contributor Author

@benashz rebased

@benashz benashz added this to the 3.5.0 milestone Apr 13, 2022
Copy link
Contributor

@benashz benashz left a comment

Choose a reason for hiding this comment

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

Looking good! I think we only need to look at adding the new fields to the acceptance tests.

Copy link
Contributor

@benashz benashz left a comment

Choose a reason for hiding this comment

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

LGTM!

Thanks again for your contribution to HashiCorp!

@benashz benashz merged commit c906db1 into hashicorp:main Apr 20, 2022
marcboudreau pushed a commit to marcboudreau/terraform-provider-vault that referenced this pull request Nov 6, 2022
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.

None yet

3 participants