Skip to content

Get secrets from OCI Vault #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
luddevik opened this issue Apr 3, 2024 · 1 comment · Fixed by #131
Closed

Get secrets from OCI Vault #72

luddevik opened this issue Apr 3, 2024 · 1 comment · Fixed by #131
Assignees

Comments

@luddevik
Copy link

luddevik commented Apr 3, 2024

Currently trying to run this in container instances in OCI. The container is set up to fetch secret from OCI Vault, by providing the VAULT_ID and VAULT_SECRET_NAME.
The common.ConfigurationProviderEnvironmentVariables("vault","") and secrets.NewSecretsClientWithConfigurationProvider(configProvider) in vault.go can not create client if not vault_tenancy_ocid, vault_user_ocid, vault_fingerprint, vault_region is defined.
This is intended to run as a standalone container in container instances and let the cotnainer be able to read the secret (without any additional users added or config files located on the container).

The dynamic group has been set up with: matching_rule = "All {resource.type='computecontainerfamily'}"
The identity policy has been set up with:
Allow dynamic-group GROUP to read vaults in tenancy
Allow dynamic-group GROUP to read secret-bundles in tenancy.

@markxnelson
Copy link
Member

Hi @luddevik and thank you for reporitng this issue. I will set up a reproducer and prepare a fix for you.

@markxnelson markxnelson self-assigned this Apr 3, 2024
@andytael andytael mentioned this issue Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants