<https://github.com/cloudposse/atmos/pull/2644> - ...
# pr-reviews
b
https://github.com/cloudposse/atmos/pull/2644 - This extends PR extend my previous above. I didn't include the change because I didn't want to do anything to delay the fix being merged. This new PR improves performance. It reduced the time it took to complete this
atmos secret list -s <stack>
against a real world stack of 72 components. With only the changes in PR 2642, it 34 seconds. While with changes in this new PR took only 21 seconds.
❌ 1
e
For context are you exclusively using SOPs?
Are you listing secrets masked or unmasked
b
Yes only SOPS. I am not using any other stores (yet) or secrets stores.
e
I think we do another optimization then; it shouldn't even need to decrypt the secrets
Then it should be sub second
b
Yeah. The command I tested with doesn't unmask the secrets.
e
21 seconds is crazy slow still
b
I agree.
e
I will take a look. Let me know whatever other rough edges you find
👍 1
b
One more piece of context, that may or may not matter. In the mentioned test of 72 components, only one had secrets defined. That's actually what surprised me the most. I didn't think it should take 30+ (or 20+) seconds list secrets when only one component had them defined. Plus the fact I wasn't unmasking the secrets.
e
Well it still has to check to see if it has a secret. I think the issue is that one of the things we do is to show an indicator whether or not that secret has been initialized.
But in an open PR we move that now to
--verify
Can you check if https://github.com/cloudposse/atmos/pull/2646 is fast now?
👀 1
b
Working as expected now. Same command completes in
0.46
seconds now.
That same (list w/o unmasking) command also worked without a live auth session. IIRC, that matches the behavior I read in the documentation a few days ago.
Prior to this PR, I pretty sure
atmos secret list
require a live auth session.
Your changes did fix
atmos secret list
because it bypasses the auth. However, the underlying
ExecuteDescribeStacks
issue remain. I was initially exposed to it because of
atmos secret list
but I can reproduce the bug with
atmos describe stack
. It affects both
ref:main
and v1.221.1. Hence the reason for this one. https://sweetops.slack.com/archives/CUJPCP1K6/p1782155729016259