Skip to content
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

Allow FetchEnvs to pull data from anywhere on a resource #251

Open
alewitt2 opened this issue Aug 5, 2021 · 0 comments
Open

Allow FetchEnvs to pull data from anywhere on a resource #251

alewitt2 opened this issue Aug 5, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@alewitt2
Copy link
Member

alewitt2 commented Aug 5, 2021

The base case im trying to solve with this is to allow a mustache template pull the resorceVersion from a cm/secret's metadata so that we can restart a deployment when it changes.

instead of key which we use to know where in the cm/secret .data section to pull from, if a user specifies path we should know to look outside the data section and pull whatever they tell us to.

Some users might want to grab whole json objects or boolean values. In this case we probably need a way to convert them into a string, so a new string type should be added to do the .toString() to the value if needed.

ex:

env:
  - name: rv # name of the key the fetched data will be assigned to
    valueFrom:
      configMapKeyRef:
        path: metadata.resourceVersion # path to key within configmap
        name: cluster-info # configmap name
        namespace: kube-system # configmap namespace
        type: string # tells fetchEnvs to stringify the fetched key if its not already
@alewitt2 alewitt2 added the enhancement New feature or request label Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant