Migrate gemspec info in project_data.yaml to the .gemspec file

Description

We currently use packaging's "package:gem" task to build the Puppet gem which adds a lot more complexity than we need (i.e. it builds a gemspec from data in project_data.yaml and then builds the corresponding default gem from it + any platform-specific gems [that might have platform-specific dependences]).

We should have the info. in project_data.yaml in the .gemspec file so that a simple gem build should do the trick.

Environment

None

Acceptance Criteria

None

Activity

Show:

Enis InanJuly 10, 2018 at 8:32 PM

This ticket's blocked on figuring out how we ultimately want to build the gem. Do we want to use the existing tooling, and hence ext/project_data.yaml, to create our gem as it is currently done? Or do we want to make the .gemspec itself buildable, taking out all gem-specific stuff from ext/project_data.yaml? The trade-off for the latter is that we will have to declare the gem deps. dynamically, which will not properly show up on the rubygems interface for listing gem dependencies. Or do we want to move towards shipping a single gem instead? Lots of questions.

Won't Do

Details

Assignee

Reporter

Team (migrated)

Platform OS

Sprint

Priority

Created May 1, 2018 at 9:36 PM
Updated September 16, 2019 at 6:52 PM
Resolved August 17, 2018 at 5:12 PM