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

cosmos_db_account - adding support for connection_strings #1194

Merged
merged 2 commits into from May 4, 2018

Conversation

thomastaylor312
Copy link
Contributor

Adds connection_strings attribute to cosmos_db_account with documentation. Also adds in some missing error handling in the same function I modified for the feature.

@tombuildsstuff tombuildsstuff changed the title feat(cosmosdb): Adds connection_strings attribute to cosmos_db_account cosmos_db_account - adding support for connection_strings May 3, 2018
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

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

Hi @thomastaylor312,

Thank you for opening this PR, it LGTM aside from this test failing:

[TestAccAzureRMCosmosDBAccount_mongoDB] [Test Output]
=== RUN   TestAccAzureRMCosmosDBAccount_mongoDB
--- FAIL: TestAccAzureRMCosmosDBAccount_mongoDB (816.94s)
	testing.go:513: Step 0 error: Check failed: 1 error(s) occurred:
		
		* Check 3/3 error: azurerm_cosmosdb_account.test: Attribute 'connection_strings' expected to be set
FAIL

Once this test passes will be more then happy to get this merged in for you 🙂

@thomastaylor312
Copy link
Contributor Author

@katbyte Thanks for the review! Where is that test output coming from? I don't see it in the travis job or when I run make test. Should I be running make testacc as well?

@thomastaylor312
Copy link
Contributor Author

Answering my own question. Looks like it. Weird that it is failing because I did a manual test as well and it had the proper output. I'll dig into it and fix

Adds connection_strings attribute to cosmos_db_account with documentation.
Also adds in some missing error handling in the same function I modified
for the feature.
@thomastaylor312
Copy link
Contributor Author

Ok, should be fixed

Updating something so teamcity can see new changes after force push.
@katbyte katbyte added this to the 1.5.0 milestone May 4, 2018
@katbyte
Copy link
Collaborator

katbyte commented May 4, 2018

Thanks, LGTM 🙂

tests now all pass:
screen shot 2018-05-04 at 14 23 00

@katbyte katbyte merged commit 7d06774 into hashicorp:master May 4, 2018
katbyte added a commit that referenced this pull request May 4, 2018
@thomastaylor312 thomastaylor312 deleted the feat/add_conn_strings branch May 4, 2018 21:30
@ghost
Copy link

ghost commented Mar 31, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants