Bengt Brodersen

I think it would be even more useful to define required labels when configure/register a new one. e.g. `./config.sh --labels "ubuntu,large:required" ...`. With this config runners should act like following:...

@tisoft thanks a lot for your deep dive. I'll try to fix it the upcoming days.

@tisoft I think you are right it is working, however the rebase involves more effort and I don't have the time right now. I maybe able to do the development...

@tisoft Unfortunately there is a challenge to make the configuration available in the ProfileSelector. I don't have the time solve this for now. I reset the branch [feature/control-profiles](https://github.com/qoomon/maven-git-versioning-extension/blob/feature/control-profiles/src/main/java/me/qoomon/maven/gitversioning/GitVersioningProfileSelector.java) and added...

Sorry I don't have time for that. Anyways thanks a lot for this awesome visualisation service

GraphQL Query to get all gists and repositories => https://github.com/antonmedv/spark/pull/6#issuecomment-1931594686

Well unfortunately using environment variables does not work for big configs :-( I make it work now with following setup. ```yaml Lifecycle: Install: RequiresPrivilege: true # to access /greengrass/v2/bin/greengrass-cli Script:...

I'm facing the same problem.

When I hit `Control`+ `C` I only get the message `Terminate signal received, exiting.` however nothing is happening after that. `'session-manager-plugin` and `aws ssm start-session --document-name 'AWS-StartPortForwardingSession' ...` process are...

My current workaround looks like this ```shell aws ssm start-session --document-name 'AWS-StartPortForwardingSession' \ --target "${INSTANCE_ID}" \ --parameters "{\"portNumber\": [\"${INSTANCE_PORT}\"], \"localPortNumber\": [\"${LOCAL_PORT}\"]}" & # WORKAROUND - stop session-manager-plugin on Ctrl +...