You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have an Argo Workflow that one can use to know if a new application version has been synced by Argo CD, and the most important, published, and running.
Why is it needed?
It will be helpful to automate execution of actions that need to happen once a new application version has been deployed, and running. My personal use case is to be able to run the TypeSense scraper once a new documentation version is up, and running in production, but I would see multiple usage for something like this by our users.
Is this missing feature preventing you from using kubefirst?
Yes
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Need to update github action workflows so that Chart URI includes generated --cluster-name as opposed to environment (ie. development, staging, production)
After updating these manually, creates derivative issue where Chart museum fails on release because it says chart already exists (if you try updating the workflow)
What is your feature idea?
I would like to have an Argo Workflow that one can use to know if a new application version has been synced by Argo CD, and the most important, published, and running.
Why is it needed?
It will be helpful to automate execution of actions that need to happen once a new application version has been deployed, and running. My personal use case is to be able to run the TypeSense scraper once a new documentation version is up, and running in production, but I would see multiple usage for something like this by our users.
Is this missing feature preventing you from using kubefirst?
Code of Conduct
The text was updated successfully, but these errors were encountered: