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

History entry labels #295

Open
seankelly001 opened this issue Feb 8, 2021 · 0 comments
Open

History entry labels #295

seankelly001 opened this issue Feb 8, 2021 · 0 comments
Labels
kind/feature A new feature request

Comments

@seankelly001
Copy link
Contributor

seankelly001 commented Feb 8, 2021

Describe the solution you'd like:
Ability to label history entries
e.g.
kconnect history label alias alias1 env=dev
kconnect history label --all env=dev

For import/export, also allow label to be applied
kconnect history export -f export.yaml -L env=prod

In batch run feature #228 , could enhance this by allowing all entries with a certain label to be run against the commands

apiVersion: kconnect.fidelity.github.com/v1alpha1
kind: RunConfig
metadata:
       name: run
spec:
 	selector:
            matchLabels:
                env: dev
 	commands:
 	- kubectl exec mypod -- somecommand
 	- kubectl logs mypod`

Why do you want this feature:
Would further enhance kconnects versatility and power, especially for ops teams needing to run commands against many clusters

@seankelly001 seankelly001 added the kind/feature A new feature request label Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A new feature request
Projects
None yet
Development

No branches or pull requests

1 participant