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

New Data Source: azurerm_eventhub_sas #22215

Merged
merged 10 commits into from
Jul 25, 2023

Conversation

neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented Jun 20, 2023

fixes #7160

image

@neil-yechenwei
Copy link
Contributor Author

@katbyte , thanks for the comment. I replied it. Please take another look. Thanks.

Copy link
Contributor

@manicminer manicminer left a comment

Choose a reason for hiding this comment

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

Per my inline comment above, I think the escape sequence issue should be fixed in the data source (or helper func, or SDK).

@neil-yechenwei
Copy link
Contributor Author

neil-yechenwei commented Jul 19, 2023

@manicminer , thanks for the comment. I replied it. Please take another look. Thanks.

image

Copy link
Contributor

@manicminer manicminer left a comment

Choose a reason for hiding this comment

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

Thanks @neil-yechenwei, is there a reason this is an untyped data source? New data sources should use the typed SDK unless there is a compelling reason not to.

@neil-yechenwei
Copy link
Contributor Author

neil-yechenwei commented Jul 20, 2023

@manicminer , I made this PR on my local about 2 years ago and this PR depends on another PR which is also submitted about 2 years ago. Given another PR is merged recently, so I submitted this PR. So shall we merge this PR first? Once I have bandwidth, I will submit another PR to convert it to typed resource. Does it make sense?

Copy link
Contributor

@manicminer manicminer left a comment

Choose a reason for hiding this comment

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

@neil-yechenwei Unfortunately I don't believe we can merge this as a new untyped resource. Can you please refactor this as a typed resource? Apologies I didn't notice this earlier in the review cycle.

@neil-yechenwei
Copy link
Contributor Author

neil-yechenwei commented Jul 21, 2023

@manicminer , I've converted it to typed resource. Please take another look. Thanks.

image

Copy link
Contributor

@manicminer manicminer 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 updating @neil-yechenwei, this LGTM 👍

@manicminer manicminer added this to the v3.67.0 milestone Jul 25, 2023
@manicminer manicminer merged commit e2791b3 into hashicorp:main Jul 25, 2023
manicminer added a commit that referenced this pull request Jul 25, 2023
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 21, 2024
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.

Shared access signature for Azure Eventhub
3 participants