thiagoelg opened a new issue, #3814:
URL: https://github.com/apache/incubator-kie-tools/issues/3814

   *This is part of a greater Dev deployments revamp.*
   
   If a repository has a directory called `.kie-sandbox/dev-deployments` with 
K8s resource YAMLs inside, KIE Sandbox should be able to use these resources to 
make a Dev deployment.
   
   ### Dealing with multiple deployment resources
   If a repository has lots of YAML resources, maybe it has different 
deployment configurations, like one for an Azure cluster, another for a local 
Kubernetes cluster, another for a specific module inside the repository, etc. 
KIE Sandbox should be able to handle these different configurations and offer 
the user a way to choose which configuration will be used in the Dev deployment.
   
   Part of this task is to think about how these different configurations will 
be arranged in the repository. Some options/considerations are:
   - If there are sub-directories inside `.kie-sandbox/dev-deployments`, each 
of them should be a separate deployment configuration;
   - Let resources be scattered, but allow users to select which YAMLs will be 
used;
   - Look for `.kie-sandbox/dev-deployments` directories in places other than 
the root of the repository;
   - ...
   
   ### Replacing tokens
   Just like with our standard Dev deployment from 
https://github.com/kiegroup/kie-issues/issues/475, users should be able to use 
tokens in their resource YAMLs and KIE Sandbox should replace them before 
making the deployment.
   
   ### Accelerators
   Create new accelerators for different Dev deployment configurations, 
including our standard one.
   Think about what configurations we need to provide (different Kubernetes 
providers, different repositories configurations, with single or multi modules, 
etc).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to