[Feature] Import should let users limit the scope

Open
  • Is something wrong?
#358 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
azure, python
Domain
cloud, infrastructure

Research direction

The issue asks for an optional resource-group filter on Azure imports, which currently cover the whole subscription through a graph query. Start by finding where the Azure import builds that query and where the import session and report record their scope. Done means the optional setting narrows the query, invalid or empty groups show a clear error, the scope appears in the report and session, and the user docs describe the option and its default. The issue is a proposal with no assignee or discussion yet, so confirm the design with maintainers first.

Written by the indexing model from the issue text.

Description

core iac service web client
Feature description

When a user imports existing infrastructure on Azure, Kumoss always works at subscription level. It looks at everything in the subscription and proposes it all for import. Users have no way to tell Kumoss that their request covers only one resource group, or a few. Import should always know the scope of the request and import every resource under that scope, and nothing outside it.

  1. Users can state the scope of an import. During request setup, the user can optionally narrow the Azure scope to one or more resource groups within the subscription.
  2. Graph query must be adapted to match the selected scope.
  3. Optional parameter, default the whole subscription
  4. The scope is visible. The session and the import report state what scope the import covered, so users and reviewers can see what "everything" meant for that run.
  5. If scope doesn't exist, is misspelled, or is empty, the user gets the error with a clear message.

Acceptance criteria

  • During import request setup in Azure, the user can optionally enter one or more resource groups in addition to the subscription.
  • Full and partial import list and propose only resources inside the given resource groups.
  • With no resource group given, import behaves as it does today.
  • The import report and the session view show the scope that was used.
  • Follow-up requests in the same session keep the original scope.
  • An invalid or empty resource group produces a clear, actionable message.
  • The scope question is not shown for providers that don't support it, or the user is told it will have no effect.
  • User documentation for importing and for making a request describes the new option and its default.
Use case or motivation

No response

Would you like to work on this?

No, I'm just proposing it

Dominant language
Python
Stars
148
Forks
8
Avg merge
12h 32m
Merged PRs (30d)
63

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from InditexTech/kumoss

All issues in InditexTech/kumoss

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.