Skip to content
This repository has been archived by the owner on Nov 7, 2019. It is now read-only.

Use Dynamo Variable Name vs S3 for ConfigMap #70

Closed
christopherhein opened this issue Sep 29, 2018 · 0 comments
Closed

Use Dynamo Variable Name vs S3 for ConfigMap #70

christopherhein opened this issue Sep 29, 2018 · 0 comments
Labels
kind/bug Something isn't working operator/dynamodb DynamoDB operator package

Comments

@christopherhein
Copy link
Contributor

No description provided.

@christopherhein christopherhein added kind/bug Something isn't working operator/dynamodb DynamoDB operator package labels Sep 29, 2018
christopherhein pushed a commit that referenced this issue Oct 1, 2018
Merge pull request #70 from christopherhein/bug/using-s3-name-vs-dynamo
9711dd7 
Use Dynamo Variable Name vs S3 for ConfigMap
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Something isn't working operator/dynamodb DynamoDB operator package
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@christopherhein