Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • v0.3.4
    Bunches of dependency updates...
    
    ...plus a couple other updates:
    
    * Better document force new
    * Add a "triggers" attribute
  • v0.3.3
    Minor tweaks; don't ForceNew on registration token change
    
    We'd long promised not to force the destruction/recreation of runner
    tokens if the registration token changes.  Now we actually honor that
    promise.
    
    _le sigh_
    
    * Use `.env` for tests
    * Don't ForceNew on registration_token change
    * Not setting RUNNER_REGISTRATION_TOKEN during acceptance tests is now
      fatal
  • v0.3.2
    Minor updates
    
    ...most behind the scenes.
    
    * use upstream structs for registration
    * allow "name" and "maintenance_notes" to be specified
  • v0.3.1
    Tests, bugfixes, etc
  • v0.3.0
    Reintroduce the gitlabci_runner_config data source
    
    Being able to programmatically construct runner configurations is rather
    nifty. (At least, I think so.) The prior way this was implemented was,
    shall we say, not sustainable.
    
    Poking around the traefik source one day, I realized I could leverage an
    internal tool of theirs to take the, um, modularly awkward
    gitlab.com/gitlab-org/gitlab-runner/common and its useful configuration
    structs and spew those structs out somewhere we could take advantage of
    them. Past that, we can generate other code using the generated code
    (insert evil laugh here) to handle the terraform schemas and read
    methods necessary.
    
    There's still some improvement to be done (the second-level code
    generator is ... um, messy), but I believe it's at a point we can start
    taking advantage of it. (Again.)
  • v0.2.6
    Internals!
    
    More updates to better talk to terraform.
    
    * Use context-aware resource method variants
    * use `tflog` for logging, rather than just `log`
  • v0.2.5
    Update the env datasource
    
    Should now reflect the current list of "Predefined environment
    variables" correctly.
  • v0.2.4
    Fix source address, etc
    
    Largely build/release/docs infrastructure changes, again.
    
    Though we do have an explicit license now, so there's that :)
  • v0.2.3
    Sign GitLab release artifacts
  • v0.2.2
    Test GitLab releasing
    
    ...one, two, three!
    
    No code changes from v0.2.1
  • v0.2.1
    Build w/go 1.17 at GitHub
    
    ...as the go.mod does kinda insist on it...
  • v0.2.0
    b2c18121 · Merge branch 'rejigger' ·
    Scaffolding, what scaffolding?
    
    This is largely a "bring it all up to dateish" release.
    
    * go to 1.17, plus modules updates
    * drop `gitlabci_runner_config` for now (until we figure out how to
      import the runner module w/o explodey)
    * include docs, etc necessary for publication on the tf registry
    * include GitHub workflow definitions to cause tags to build releases on
      GitHub (mirror-pushed from GitLab)
    * other general updates
    
    Really, the only big, user-noticeable thing should be that the config
    data-source went away.  Hopefully that won't be for long, though.
  • v0.1.0
    6e05afa4 · Merge branch 'doc' ·
    v0.1.0; new data sources
    
    Added:
    
    * `gitlabci_runner_config`
    * `gitlabci_environment`
  • v0.0.1
    48006eb9 · Add release-creating job ·
    Initial release
    
    We build, we work.  Time to actually build/release.