Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[BUG]Removal of subscription Folder from Artifacts Deletes All Subscriptions in APIM Instance

未关闭
#655 9 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
azure, csharp
领域
api, cloud

调研方向

从 artifacts 目录中移除 subscription 文件夹,并部署到 Azure API Management 实例,以重现该问题。将生成的 subscriptions 与预期行为进行比较,并检查 configuration..yaml 中的值是如何应用的;当现有 subscriptions 保持不变且配置覆盖按预期工作时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

Release version

v6.0.1.1

Describe the bug

It has been observed that when the subscription folder is removed from the artifacts, it results in the deletion of all subscriptions present in the Azure API Management (APIM) instance. This is a critical issue because it leads to unintended loss of subscriptions and disrupts the management of API access.

Impact:
Data Loss: Loss of all subscriptions in the APIM instance can lead to significant disruptions in service and access control.
Configuration Management: Failure to override values from the .yaml file can result in inconsistent and unexpected behavior.

kindly provide the solution.

Expected behavior

Removing the subscription folder should not affect existing subscriptions in the APIM instance. Instead, the process should handle this folder appropriately without deleting existing data or should provide a warning about potential impacts.

Actual behavior

The removal of the subscription folder leads to the deletion of all existing subscriptions in the APIM instance.
Additionally, the configuration values from the configuration..yaml file are not being overridden as expected.

Reproduction Steps

Remove the subscription folder from the artifacts directory.
Deploy the artifacts to the APIM instance.
Observe that all existing subscriptions in the APIM instance are deleted.

主要语言
C#
星标
449
派生
248
PR 合并指标
30 天内没有已合并 PR

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/apiops 的其他 Issue

查看 Azure/apiops 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。