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

Ignore order for reply_urls #61

Merged
merged 2 commits into from
Apr 12, 2019

Conversation

cgroschupp
Copy link
Contributor

Use TypeSet for reply_urls to ignore order.

@ghost ghost added the size/XS label Mar 13, 2019
@cgroschupp cgroschupp force-pushed the feature/fix_reply_urls_order branch from e9c7865 to f811277 Compare March 13, 2019 12:43
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.

Thanks for the PR @cgroschupp, order definitely shouldn't matter here.

This LGTM except you are going to need to update an acceptance test:

------- Stdout: -------
=== RUN   TestAccAzureADApplication_update
=== PAUSE TestAccAzureADApplication_update
=== CONT  TestAccAzureADApplication_update
--- FAIL: TestAccAzureADApplication_update (3.94s)
    testing.go:538: Step 1 error: Check failed: Check 7/8 error: azuread_application.test: Attribute 'reply_urls.0' not found
FAIL

@cgroschupp
Copy link
Contributor Author

cgroschupp commented Mar 25, 2019

@katbyte I haven't found a solution except to set reply_url to a fixed string to get a static set ID. I hope that's okay.

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.

Thats perfect @cgroschupp 🙂 that you for making that change. LGTM 🚀

@katbyte katbyte merged commit e39a408 into hashicorp:master Apr 12, 2019
@katbyte katbyte modified the milestones: v0.4.0, v0.3.0 Apr 12, 2019
katbyte added a commit that referenced this pull request Apr 12, 2019
@ghost
Copy link

ghost commented May 12, 2019

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!

@ghost ghost locked and limited conversation to collaborators May 12, 2019
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.

2 participants