Skip to content

Support for API Management Features for APIM Workspaces #27937

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

Closed
1 task done
JackBruceShell opened this issue Nov 7, 2024 · 3 comments
Closed
1 task done

Support for API Management Features for APIM Workspaces #27937

JackBruceShell opened this issue Nov 7, 2024 · 3 comments

Comments

@JackBruceShell
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

Any timeline on implementing azurerm features for API Management Workspaces and all of the inner workings of Workspaces?

New or Affected Resource(s)/Data Source(s)

azurerm_api_management_api

Potential Terraform Configuration

resource "azurerm_api_management_workspace"
resource "azurerm_api_management_workspace_api"
resource "azurerm_api_management_workspace_api_operation"
etc...

References

No response

@JackBruceShell
Copy link
Author

#21109

Waiting for this features since the referenced ticket. This is much needed now since APIM Workspaces are now GA.

Thanks.

@rcskosir
Copy link
Contributor

rcskosir commented Nov 8, 2024

Thanks for taking the time to submit this issue. This is a duplicate of #21109. We like to try to keep discussions consolidated, so we’re going to close this new issue in favor of #21109.

@rcskosir rcskosir closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2024
Copy link

github-actions bot commented Dec 9, 2024

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 have found a problem that seems similar to this, 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 Dec 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants