bitsofinfo / cicdstatemgr Goto Github PK

Refine slack integration to be a module/plugin or just cleanup the configuration specification to get rid of references to "slack" as it can really be used to send data to any endpoint.

Would like to have new 1st glass feature for generating additional "state" data based on the current state that can be generated on demand. This would be configured in app pipeline config files under the classification generators.

Each generator would have an if which if yields a value, then proceeds to set multiple key/value pairs rendered via jinja2

For example:

cicd-contexts:
  dev:
    pipelines:
      build:
        generators:
         dockerfile:
            alpine:
              if: "{%- 'alpine' in state.gitTag -%}true{%- endif -%}"
              set:
                - key: "state.build.targetImageName"
                  value: "{{state.gitAppName}}"
                - key: "state.build.generateDockerfileCmd"
                  value: |
                    ./gendockerfile.sh \
                        -f alpine:latest \
                        -x {{state.gitTag}} 
                        
            centos:
              if: "{%- 'centos' in state.gitTag -%}true{%- endif -%}"
              set:
                - key: "state.build.targetImageName"
                  value: "{{state.gitAppName}}"
                - key: "state.build.generateDockerfileCmd"
                  value: |
                    ./gendockerfile.sh \
                        -f centos:latest \
                        -x {{state.gitTag}} 
       

The operator could then call:

        cicdstatemgr \
          --secrets cicdstatemgr-secrets.yaml  \
          --config cicdstatemgr-config.yaml \
          --id cicd-context-data-id-X \
          --generate pipelines.build.generators.dockerfile 

Which would then yield the matching key/value pairs in the generator config into the cicdContextData state.

Some flow patterns redefined across various bases can have the need to just be templated themselves or re-used entirely

.sh source file: "File name too long" on jinja2macros or long values

Need an option to truncate or omit values beyond a certain length

https://github.com/SPSCommerce/redlock-py

Need to permit derivative app pipeline config files to toggle enable/disable of inherited event-handlers configs

i.e. if enabled: True|False is present, the event handler will be skipped

Currently it is assumed enabled and there is not way for something to be disabled/removed due to the merging routing

--tmpl-ctx-vars where expression/value contains = sign is not splitting correctly

add jinja2 filter to make variable contents JSON safe from an escaping standpoint

Currently the only event handler that supports multiple actions for a given handler is the set-values type. This needs to be extended to notify, trigger-pipeline etc