Skip to content
This repository has been archived by the owner on Oct 8, 2023. It is now read-only.

use google/aws secret manager or azure Key Vault instead of local file cache to store long-lived token? #13

Open
grimmer0125 opened this issue Dec 15, 2021 · 0 comments
Open

use google/aws secret manager or azure Key Vault instead of local file cache to store long-lived token? #13

grimmer0125 opened this issue Dec 15, 2021 · 0 comments

Comments

@grimmer0125
Copy link
Member

No description provided.

@grimmer0125 grimmer0125 changed the title use google/aws/azure secret manager instead of local file cache to store long-lived token? use google/aws/azure secret manager or Key Vault instead of local file cache to store long-lived token? Dec 15, 2021
@grimmer0125 grimmer0125 changed the title use google/aws/azure secret manager or Key Vault instead of local file cache to store long-lived token? use google/aws secret manager or azure Key Vault instead of local file cache to store long-lived token? Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grimmer0125