https://cloudposse.com logo
Join Slack
Powered by
:wave: Hello. Is is possible to delete/unset a sta...
# atmos
k
šŸ‘‹ Hello. Is is possible to delete/unset a stack-scoped secret? For example: I ran 
atmos init -s organization
w/ the following configured in `mixins/organization`:
Copy code
secrets:
  vars:
    CLOUDFLARE_ZONE_ID:
      sops: organization
      required: true
I then attempted to run 
atmos unset CLOUDFLARE_ZONE_ID -s organization
however this prompts me to select a component. I'm using 
Atmos 1.233.2 on linux/amd64
Thanks for any help.
Copy code
atmos secret list

 Stack         Component  Secret              Scope  Provider           Status
ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€ā”€
 organization  *          CLOUDFLARE_ZONE_ID  stack  sops:organization  initialized
e
however this prompts me to select a component.
This sounds like something we fixed in the upcoming 1.234.0 release
I then attempted to run 
atmos unset
I believe the command is 
atmos secret delete
k
Oops, I meant 
atmos secret unset
(alias of 
delete
).
> This sounds like something we fixed in the upcoming 1.234.0 release šŸŽ‰ Yay! I had a similar experience w/ 
atmos secret shell
where I was expecting 
component
to be optional. Not sure if that was also addressed in 
1.234.0
but I can open a GH issue if not šŸ™‚
e
....confirming
Ok, so it was partially fixed. Will address this now.
k
Awesome! Thank you so much for all of your help on this (and all of the other issues I've previously reported). šŸŽ‰ šŸŽ‰šŸŽ‰
šŸ™‡ā€ā™‚ļø 1
e
Open in Slack
Previous
Powered by