Skip to content

1.1.6

Choose a tag to compare

View all tags
@gyurix1968 gyurix1968 released this 11 Oct 09:57
· 128 commits to main since this release
1.1.6
df9af22

Release v1.1.6

Highlights

  • Version constant updated to 1.1.6.
  • Conditional Docker registry authentication (only if both username and password are provided).
  • Configurable framework scheduler image/name/network/subnet/version via environment variables.
  • Optional debug mode to keep container alive for interactive inspection.
  • Drone CI pipeline integration (automated build, test, multi-tag push).

Entrypoint Changes

  • Introduced conditional login: docker login $DOCKER_REGISTRY_URL only runs when credentials are present.
  • Added dynamic pass-through of registry credentials to child container (via composed DOCKER_REGISTRY_ENVS).
  • Environment defaults established / confirmed:
    • DOCKER_REGISTRY_URL (override-friendly; default masked)
    • GLOBAL_VERSION=latest
    • SERVICE_DIR=/etc/user/config/services
    • SECRET_DIR=/etc/user/secret
    • SHARED=/var/tmp/shared
    • FRAMEWORK_SCHEDULER_IMAGE=framework-scheduler
    • FRAMEWORK_SCHEDULER_NAME=framework-scheduler
    • FRAMEWORK_SCHEDULER_NETWORK=framework-network
    • FRAMEWORK_SCHEDULER_NETWORK_SUBNET=172.19.255.0/24
    • FRAMEWORK_SCHEDULER_VERSION=latest
    • RUN_FORCE=false
    • DEBUG_MODE=false (set to true for interactive shell)
  • Debug mode now replaces normal start with long-running sleep shell (sleep 86400).

Drone CI Integration

  • Pipeline automates: lint/test → build → multi-tag (full, major.minor, major, latest) → push.
  • Uses secrets store for registry credentials (no hardcoded values).
  • Supports injecting version via environment (e.g. FRAMEWORK_SCHEDULER_VERSION).
  • Optional debug / dry-run step can align with DEBUG_MODE=true.

Upgrade Notes

  • Set both DOCKER_REGISTRY_USERNAME and DOCKER_REGISTRY_PASSWORD to enable registry login; otherwise it is skipped.
  • Review custom subnet (FRAMEWORK_SCHEDULER_NETWORK_SUBNET) to avoid conflicts with existing Docker networks.
  • Use DEBUG_MODE=true only for troubleshooting (container will not run normal workload).
  • Define RUN_FORCE=true only if future logic depends on forcing redeploy (behavior currently placeholder).

Security / Confidentiality

  • No sensitive hostnames or credentials are embedded in the script.
  • Ensure secrets are supplied through your CI secret management (not committed).

Changelog Summary

  • Added: Conditional registry auth, debug mode, network subnet configurability.
  • Changed: Version constant to 1.1.6; clarified env defaults.
  • CI: Added Drone pipeline for automated build/test/publish.

Next Steps

  • Document intended semantic of RUN_FORCE.
  • Add health check or timeout for debug mode.
  • Extend tests to validate network creation and credential pass-through.
Assets 2
Loading