Selective auto-update options

[nwish]

Howdy! I've been on a quest to try and implement selective / scheduled auto updates via the Actions functionality and I'm hitting a brick wall.

Using an action on a schedule, combined with auto update pulls in the stack settings (not redeployments, since I don't want everything just redeploying whenever), we can easily tell Komodo to redeploy all stacks with updates.

However, I have not found a way to designate specific stacks, or even at a more granular level, containers that are allowed to auto redeploy on the schedule.

I've looked at:

• stack tags (can't seem to access stack tags via API)
• container labels (I have not found a way to iterate the containers in a specific stack to then find labels, or simply iterate ALL containers and then attribute them to a stack to fire the redeployment on)
• listing eligible stacks in an array before running a "fire redeployments on these stacks" script (this is the closest I've come, and it does work, but I want to not have to update the script every time I have a new stack)

It seems like if we could get tags (the ones created in the web UI) tied to stacks and containers, this would be a breeze!

Basically, I want:

• stacks that never auto update, but new images are still auto pulled to tell me there's an update
• stacks that fully auto update (using scheduled actions) either the whole stack, or certain containers within the stack

Any other thoughts?

[mirisbowring]

Hi, i would like to follow this questions.
I am deploying my services via "Infrastructure as Code". So basically i have everything configured in a git repo and if anything changes, my stacks are redeployed (if changed).

Today I started migratig more curcial services to komodo like my backup setup. Currently i have a wildcard * set for the batch deploy filter.

Now i would like to batch deploy everything except the S3 Stack and the Backrest Stack. Imagine, i would change a config in git and komodo would redploy while doing a backup!!!

I added thematic labels like prod backup infrastructure to be able to filter for specific workloads, but unfortunately, i cannot work with them in the procedures.

I think, a "filter" stage would be nice! then i could filter for e.g. a specific label and if it is not present, the stage / procedure would cancel or something like this.