<#4114 [BUG] flytectl update un-archives objects w...
# flyte-github
a
#4114 [BUG] flytectl update un-archives objects when updating their properties without both --activate and --archive flags Issue created by kamaleybov Describe the bug If an object is archived, and I update any property except state (e.g., description), the object is unarchived. Here's an example with projects:
Copy code
$ flytectl get project
 --------------- --------------- ---------------------------
| ID            | NAME          | DESCRIPTION               |
 --------------- --------------- ---------------------------
| flyteexamples | flyteexamples | flyteexamples description |
 --------------- --------------- ---------------------------
| flytetester   | flytetester   | flytetester description   |
 --------------- --------------- ---------------------------
| flytesnacks   | woopidoo      | oops2                     |
 --------------- --------------- ---------------------------
3 rows

$ flytectl update project --id flytesnacks --archive
Project flytesnacks updated

$ flytectl get project
 --------------- --------------- ---------------------------
| ID            | NAME          | DESCRIPTION               |
 --------------- --------------- ---------------------------
| flyteexamples | flyteexamples | flyteexamples description |
 --------------- --------------- ---------------------------
| flytetester   | flytetester   | flytetester description   |
 --------------- --------------- ---------------------------
2 rows

$ flytectl update project --id flytesnacks --description "bananas"
Project flytesnacks updated

$ flytectl get project
 --------------- --------------- ---------------------------
| ID            | NAME          | DESCRIPTION               |
 --------------- --------------- ---------------------------
| flyteexamples | flyteexamples | flyteexamples description |
 --------------- --------------- ---------------------------
| flytetester   | flytetester   | flytetester description   |
 --------------- --------------- ---------------------------
| flytesnacks   | woopidoo      | bananas                   |
 --------------- --------------- ---------------------------
3 rows
Expected behavior Objects should stay in whatever state they were prior to update. Additional context to reproduce 1. Archive an object. 2. Update any property except state (e.g., do not use
--activate
or
--archive
flags). 3. Get the object and see that its state changed to active. Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte