Expose tagging capabilities to main objects (tasks, secrets, webhook configs, etc)

Open
#357 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend-api-design

Research direction

Start by locating the existing set_workflow_tags method and the SDK entry points for secrets, webhook configs, and tasks. Compare how those objects are represented and determine the tagging methods needed for each. Done means the requested major objects can be tagged through the Python SDK without manual inventory changes.

Written by the indexing model from the issue text.

Description

enhancement

Hello there,

aiming to have a full managed inventory recorded on our git repository, and also aiming to rely on tags for application IAM management, we would like to have methods to be able to tag all the major objects in conductor/orkes (secrets, webhook configs, tasks).

Otherwise, devs adding a new object into the orkes/conductor inventory leads to manual tagging of that object.
We managed to achieve a smooth setup for workflow which we use the set_workflow_tags method.

Thank you

Dominant language
Python
Stars
104
Forks
43
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

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 conductor-oss/python-sdk

All issues in conductor-oss/python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.