dut 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: bd9f20373355d4e361156aeff57feebff793bef7b580adce65db1a7a2a1ef9d3
+  data.tar.gz: 42dbab45d107aaf4c5650b7d88cff2bb8cce6562bf971a2b4b8fbeeb126e50b8
+SHA512:
+  metadata.gz: e15830034534b0df35c4c372bc7f482d56c3673d9e90a3dfc946a9e24fa9691ad1d3923670039862b0ea128bfee9cf44fda77af7895f21b3750a8705572471fa
+  data.tar.gz: 42a399e3144c5f8d0617a2493e78c21a67c2c181d0bacccdcc335ef5e27756b692a71d50c9803f732c5c879a3b13ac2fdd963da445a9d13bdc2b088cee2945b1

data/.circleci/config.yml

@@ -0,0 +1,134 @@
+version: 2.1
+
+orbs:
+  gem: doximity/gem-publisher@0
+
+executors:
+  ruby-latest:
+    resource_class: small
+    docker:
+      - image: circleci/ruby:latest
+        environment:
+          BUNDLE_VERSION: "~> 2.3"
+
+# yaml anchor filters
+master_only: &master_only
+  filters:
+    branches:
+      only: master
+    tags:
+      ignore: /.*/
+
+pr_only: &pr_only
+  filters:
+    branches:
+      ignore: master
+    tags:
+      ignore: /.*/
+
+version_tags_only: &version_tags_only
+  filters:
+    branches:
+      ignore: /.*/
+    tags:
+      only: /^v.*/
+
+jobs:
+  build:
+    executor: ruby-latest
+    steps:
+      - checkout
+      - run:
+          name: Install Bundler specific version
+          command: |
+            gem install bundler --version "${BUNDLE_VERSION}" --force
+            bundle config set --local path 'vendor/bundle'
+            bundle config set --local frozen 'true'
+            bundle config set --local jobs '4'
+            bundle config set --local retry '3'
+      - restore_cache:
+          keys:
+            - v1-bundle-{{ checksum "Gemfile.lock" }}-
+      - run:
+          name: Install Ruby Dependencies
+          command: bundle install --local
+      - save_cache:
+          key: v1-bundle-{{ checksum "Gemfile.lock" }}-
+          paths:
+            - vendor/bundle
+      - run:
+          name: Run Rubocop
+          command: bundle exec rake ci:rubocop
+      - run:
+          name: Run Tests
+          command: bundle exec rake ci:specs
+      - store_test_results:
+          name: Store test results
+          path: tmp/test-results
+      - run:
+          name: Build documentation
+          command: bundle exec rake ci:doc
+      - store_artifacts:
+          name: Saves documentation
+          path: doc
+      - persist_to_workspace:
+          root: .
+          paths:
+            - vendor/bundle
+
+workflows:
+  version: 2
+
+  trunk:
+    jobs:
+      - build:
+          <<: *master_only
+      - gem/build:
+          <<: *master_only
+          executor: ruby-latest
+          name: gem-build
+          requires:
+            - build
+
+  pull-requests:
+    jobs:
+      - build:
+          <<: *pr_only
+      - gem/build:
+          <<: *pr_only
+          executor: ruby-latest
+          name: gem-build
+          requires:
+            - build
+      - pre-release-approval:
+          <<: *pr_only
+          type: approval
+          requires:
+            - gem-build
+      - gem/publish:
+          <<: *pr_only
+          name: gem-publish
+          to_rubygems: true
+          pre_release: true
+          requires:
+            - pre-release-approval
+          context: artifact_publishing
+
+  final-release:
+    jobs:
+      - build:
+          <<: *version_tags_only
+      - gem/build:
+          <<: *version_tags_only
+          executor: ruby-latest
+          name: gem-build
+          requires:
+            - build
+      - gem/publish:
+          <<: *version_tags_only
+          name: gem-publish
+          to_rubygems: true
+          pre_release: false
+          requires:
+            - gem-build
+          context: artifact_publishing

data/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Back-end team
+* @doximity/mofo_backend

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+Overview
+--------
+
+<!-- High-level description of what is being changed and why. -->
+
+Technical Details
+-----------------
+
+<!-- Explain non-obvious technical changes, the reasoning behind them, any compromises involved, etc.
+(Remove this section if you have nothing to add here.) -->
+
+Testing Instructions
+---------------
+
+<!-- Please replace this with testing instructions. -->

data/.gitignore

@@ -0,0 +1,8 @@
+.rspec_status
+/*.gem
+/.bundle/
+/coverage/
+/doc/
+/pkg/
+/tmp/
+/vendor/bundle/

data/.rubocop.yml

@@ -0,0 +1,17 @@
+require:
+- rubocop-rails
+
+Style/StringLiterals:
+  Enabled: false
+
+Metrics/BlockLength:
+  Enabled: false
+
+Naming/FileName:
+  Enabled: false
+
+Naming/MethodParameterName:
+  Enabled: false
+
+Rails/RakeEnvironment:
+  Enabled: false

data/.ruby-version

@@ -0,0 +1 @@
+2.7.5

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+Changelog
+=========
+
+## 0.0.1 - 05/26/2022
+  * Initialize gem

data/CONTRIBUTING.md

@@ -0,0 +1,245 @@
+# Contributing
+
+This document lists the current best the practices adopted by the team to provide a consistent workflow that contributes
+to high quality code, improves communication of behaviors, reduce noise and helps automate common activities.
+
+Please read this with attention and respect the suggestions when contributing.
+
+## Table of Contents
+
+1. [Code, Architecture and APIs](#code-architecture-and-apis)
+2. [Development, Refactoring and Tests](#development-refactoring-and-tests)
+    1. [Good Practices](#good-practices)
+    2. [Test (As a living documentation)](#test-as-a-living-documentation)
+3. [Git](#git)
+    1. [Workflow](#workflow)
+    2. [Commit Style Guide](#commit-style-guide)
+    3. [Template](#template)
+    4. [Changelog Types](#changelog-types)
+    5. [Branch Style Guide](#branch-style-guide)
+4. [Visual Changes](#visual-changes)
+5. [Debug and bug report](#debug-and-bug-report)
+
+## Code, Architecture and APIs
+
+We embrace the principles of Domain Driven Design[^ddd] and Hexagonal Architecture[^hexagonal-architecture] because we
+believe they provide a strong foundation in terms of communication of internal behaviors and the decoupling of components
+of the system using layers.
+One of the values of the team is to improve the _User Experience (UX)_ and _Developer Experience (DevEx)_ of the users
+and developers using the system by providing solutions that are easy to adopt and easy to understand, independently of
+previous experience. Therefore we direct the development and the acceptance of Pull Requests to align to these premisses.
+This aims to permit that product and stream-aligned teams focus solely in the core subject of their systems and do not
+waste time on setup and understanding of platforms and support systems.
+
+[^ddd]: https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215/ref=sr_1_1?crid=3CKS9W9SZNMXM&keywords=domain+driven+design&qid=1644428951&sprefix=domain+driven+desig%2Caps%2C205&sr=8-1
+[^hexagonal-architecture]: https://en.wikipedia.org/wiki/Hexagonal_architecture_(software)
+
+## Development, Refactoring and Tests
+
+We apply _Test Driven Development_[^tdd][^tdd-better-software] and expect any contribution to do the same, following the
+_red-green-refactor_ cycle. To improve immediate feedback on the changes and minimize long unsaved changes that might
+break behavior, run `guard` with the provided `Guardfile` so that the specs for the code under development are run as
+soon as the file is saved.
+Save after every line change ideally[^sandy-books].
+
+It is possible to run `guard` for an app with or without `*-test` container or for a gem:
+
+#### App with no test container
+
+      dox-do bundle exec guard
+
+#### App with test container
+
+      dox-dc exec dox-dut-service-test bundle exec guard
+
+#### Gem (from any light app, `foundation` in this case)
+
+      dox-dc exec foundation bash -c "cd /opt/dox-gems/dox-messaging && BUNDLE_GEMFILE=\`pwd\`/Gemfile bundle exec guard"
+
+### Good Practices
+
+**FAVOR**: Make concepts explicit and clear to users of the system  
+**FAVOR**: Use _interfaces_ over implementation  
+**FAVOR**: Keep implementation details in deeper layers  
+**FAVOR**: Leave the code better than you found  
+**FAVOR**: _Refactor_ judiciously during development  
+**FAVOR**: _Object_, _Methods_ and _Composition_ instead of class methods  
+**FAVOR**: Use explicit method declarations instead of meta-programming  
+
+By using the above suggestion of TDD this will be natural as _Class_ methods and meta-programming are harder to test,
+harder to use, harder to debug and ultimately less communicative.
+
+Follow **CUPID**[^cupid] properties:
+- [**C**omposable](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#composable): plays well with others
+- [**U**nix philosophy](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#unix-philosophy): does one thing well
+- [**P**redictable](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#predictable): does what you expect
+- [**I**diomatic](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#idiomatic): feels natural
+- [**D**omain-based](https://dannorth.net/2022/02/10/cupid-for-joyful-coding/#domain-based): the solution domain models the problem domain in language and structure
+
+**AVOID**: the use _meta-programming_ and procedural code hidden in non-concept related "object" objects like the _Rails
+Service Object_ (which is not a service from the DDD definition[^ddd]). Consider a more object oriented approach and
+consult good references for it regarding naming, responsibilities, methods, etc, like the following:
+[Your coding conventions are hurting you](http://www.carlopescio.com/2011/04/your-coding-conventions-are-hurting-you.html),
+[Enough With the Service Objects Already](https://avdi.codes/service-objects/),
+[Beware of “service objects” in Rails](https://www.codewithjason.com/rails-service-objects/)
+
+[^tdd]: https://en.wikipedia.org/wiki/Test-driven_development#Test-driven_development_cycle
+[^tdd-better-software]: https://www.youtube.com/watch?v=fSvQNG7Rz-8
+[^sandy-books]: https://sandimetz.com/products
+[^cupid]: https://dannorth.net/2022/02/10/cupid-for-joyful-coding/
+
+### Test (As a living documentation)
+
+We apply _BDD (Behavioral Driven Design)_ with _Rspec_ as our preferred tool to test and they provide the best
+combination of easy to write and powerful specs and clear communication of intent via behavior description.
+_BDD_ is focused on the behavior of the system or part of it, not methods. Secondly, Unit test refers to a system's unit,
+not a method as well. So a Car class, for instance, is a Unit in the system and its unit tests mock all its dependencies
+and test its behavior in isolation.
+Therefore, we do not use _method_ names in specs and clearly define the behavior so intent is clearly documented for future
+developers. For a longer description with examples, consult a
+[response to BetterSpecs](https://github.com/betterspecs/betterspecs/issues/2#issuecomment-894498097)
+Focus on the **WHAT** and not in the **HOW**[^bdd-what].
+
+[^bdd-what]: https://www.youtube.com/watch?v=YAZr3LsCzn0
+
+## Git
+
+### Workflow
+
+The workflow follows four simple rules:
+
+1. (main|master) is always deployable (no broken commits / with failing specs)
+2. always rebase (`git pull --rebase`)
+3. short-lived branches
+    1. aim for 1 day maximum and avoid keeping branches alive for more than 2-3 days
+4. rebase branch over (main|master) before Merge Request (`git rebase master` from inside the branch)
+    1. avoid automatic generated merges in the branch direction
+
+We prefer a trunk-based workflow and branch by abstraction with feature flags[^ci-vs-branches][^ci-feature-branching]
+and do not use `git-flow` or similar as they hinder quality by delaying integration[^no-gitflow]. We accept some
+limitations of `Github-flow`[^github-flow] given the remote nature of the company, but prefer _rebase_ over _merge_ to
+get a cleaner history of branches when they are to be merge to main/master.
+**DO NOT** squash[^no-squash] when merging. If needed be, use `--squash` or `--fixup` options for minor fixes to
+commits on branches.
+
+[^ci-vs-branches]: https://www.youtube.com/watch?v=v4Ijkq6Myfc
+[^ci-feature-branching]: https://www.youtube.com/watch?v=lXQEi1O5IOI
+[^no-gitflow]: https://www.youtube.com/watch?v=_w6TwnLCFwA
+[^github-flow]: https://githubflow.github.io/
+[^no-squash]: https://blog.ploeh.dk/2020/10/05/fortunately-i-dont-squash-my-commits/
+
+### Commit Style Guide
+
+The commit style follow good practices listed in ["What makes a good commit message"](https://dev.to/cvortmann/what-makes-a-good-commit-message-181i)
+and related post. These practices were turned into a template[^message-template] that is used whenever you
+`git commit` and setup via git config[^template-config] (See below).
+This template also uses git trailer information (after the ---) to avoid clogging the message with non important
+information and reduce unnecessary noise.
+Use trailer information for any extra information like Jira card number, Pivotal ticket, Changelog, etc. The Jira card
+number is automatically infered from the branch name when using the [format below](#branch-style-guid).
+**AVOID** using these references on the title of the commit as well as the body when not necessary (like a link).
+**AVOID** emojis in the title or body of commit, restrict them to the Github UI.
+
+To setup the template and hooks use the following:
+
+      .config/git/setup
+
+The two main trailers are:
+- Jira-issue *or* Github-issue (when applied)
+- Changelog
+
+Specifying the [Changelog type](#changelog-types) correctly also helps to create more atomic commit with single
+responsibility instead of adding everything in one commit.
+The correct analogy to a commit is a `release` that would go directly to production instead of a `save button` that
+adds all the changes at once.
+Use `git add -p` to add just the needed changes and review them with `git diff --staged`.
+Our end goal is to create high quality commit in branch as they were going directly to (main|master).
+For a style checker you can use this hook[^hook] and this setup[^hook-setup] to make it available to all repos.
+This is not enforced today, but might be automated in the future.
+
+[^message-template]: https://github.com/jvortmann/dots/blob/main/git/message
+[^template-config]: https://github.com/jvortmann/dots/blob/85d1798cf6145a36196909e4cf3898a44c159e91/git/config#L43
+[^hook]: https://github.com/jvortmann/dots/blob/main/git/hooks/commit-msg
+[^hook-setup]: https://github.com/jvortmann/dots/blob/85d1798cf6145a36196909e4cf3898a44c159e91/git/config#L40
+
+#### References
+
+- <http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html>
+- <https://dev.to/cvortmann/what-makes-a-good-commit-message-181i>
+- <http://karma-runner.github.io/0.10/dev/git-commit-msg.html>
+- <https://github.com/agis-/git-style-guide>
+
+### Template
+
+    Summarize changes in around 50 characters or less
+
+    More detailed explanatory text, if necessary. Wrap it to about 72
+    characters or so. In some contexts, the first line is treated as the
+    subject of the commit and the rest of the text as the body. The
+    blank line separating the summary from the body is critical (unless
+    you omit the body entirely); various tools like `log`, `shortlog`
+    and `rebase` can get confused if you run the two together.
+
+    Explain the problem that this commit is solving. Focus on why you
+    are making this change as opposed to how (the code explains that).
+    Are there side effects or other unintuitive consequences of this
+    change? Here's the place to explain them.
+
+    Further paragraphs come after blank lines.
+
+     - Bullet points are okay, too
+
+     - Typically a hyphen or asterisk is used for the bullet, preceded
+       by a single space, with blank lines in between, but conventions
+       vary here
+
+    ---
+
+    Jira-issue: MS-414
+    Github-action: close|fix|resolve #414
+    Changelog: feature|refactor|fix|doc|style|test|chore
+    Refactoring: removeDeadCode
+    See-also: 6ed2658fb9c4a9e93e3216f32071c030f14d7d28
+
+Commit examples: [310aa9](https://github.com/doximity/dox-messaging/commit/310aa913d95ef465d17fc5886e719ebf2efb3192),
+[7bb4b5](https://github.com/doximity/dox-messaging/commit/7bb4b5ed2ddfbea3705101d26023a63d2fc085d4),
+[b9e069](https://github.com/doximity/dox-messaging/commit/b9e06944251963cfdb7cb02cc0232f2f3994a024),
+[5f84d7](https://github.com/doximity/dox-messaging/commit/5f84d7c160888b4c6ca8b5b8db361537c2ea0e61),
+[667a50](https://github.com/doximity/dox-messaging/commit/667a50a46659ae20721efc6e8be4ff9e3768a7d7).
+
+### Changelog Types
+
+- `feature`: Change behavior, interface or adds new functionality
+- `fix`: Fix bugs
+- `doc`: Change to documentation, README, CHANGELOG etc
+- `style`: Format, missing semi colons, changes in whitespace, coding style in general
+- `refactor`: Refactor production code, no functionality or behavior change, move method, rename variables
+- `test`: Add missing tests, improve tests; no production code change
+- `chore`: Update gems; no production code change
+
+Check the existing commits for examples of each type.
+
+### Branch Style Guide
+
+The branches use the following template:
+
+    {jira-issue-number}/{dash-separated-card-title}
+
+Example: `git switch -c MS-414/add-contributing-document`
+
+## Visual changes
+
+When opening a merge request that contains visual changes, it is recommended to add an image, video or GIF of the change.
+Giphy Capture can be used: <https://giphy.com/apps/giphycapture>
+
+## Debug and bug report
+
+Rely on error messages to identify potential issues or direct a debugging session.
+When opening a bug report, provide
+all information possible, like:
+- gem version
+- ruby version
+- full stack-trace
+- log entries
+- steps to reproduce
+

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in omniauth-doximity.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,85 @@
+PATH
+  remote: .
+  specs:
+    dut (0.0.1)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (7.0.3)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+    ast (2.4.2)
+    concurrent-ruby (1.1.10)
+    diff-lcs (1.5.0)
+    i18n (1.10.0)
+      concurrent-ruby (~> 1.0)
+    minitest (5.15.0)
+    parallel (1.22.1)
+    parser (3.1.2.0)
+      ast (~> 2.4.1)
+    psych (4.0.4)
+      stringio
+    rack (2.2.3)
+    rainbow (3.1.1)
+    rake (11.3.0)
+    rdoc (6.4.0)
+      psych (>= 4.0.0)
+    regexp_parser (2.4.0)
+    rexml (3.2.5)
+    rspec (3.11.0)
+      rspec-core (~> 3.11.0)
+      rspec-expectations (~> 3.11.0)
+      rspec-mocks (~> 3.11.0)
+    rspec-core (3.11.0)
+      rspec-support (~> 3.11.0)
+    rspec-expectations (3.11.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-mocks (3.11.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-support (3.11.0)
+    rspec_junit_formatter (0.5.1)
+      rspec-core (>= 2, < 4, != 2.12.0)
+    rubocop (1.30.0)
+      parallel (~> 1.10)
+      parser (>= 3.1.0.0)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml (>= 3.2.5, < 4.0)
+      rubocop-ast (>= 1.18.0, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 3.0)
+    rubocop-ast (1.18.0)
+      parser (>= 3.1.1.0)
+    rubocop-rails (2.14.2)
+      activesupport (>= 4.2.0)
+      rack (>= 1.1)
+      rubocop (>= 1.7.0, < 2.0)
+    ruby-progressbar (1.11.0)
+    sdoc (2.4.0)
+      rdoc (>= 5.0)
+    stringio (3.0.2)
+    tzinfo (2.0.4)
+      concurrent-ruby (~> 1.0)
+    unicode-display_width (2.1.0)
+
+PLATFORMS
+  x86_64-darwin-21
+  x86_64-linux
+
+DEPENDENCIES
+  bundler (~> 2.3.12)
+  dut!
+  rake (~> 11.2, >= 11.2.2)
+  rspec (~> 3.11)
+  rspec_junit_formatter
+  rubocop (~> 1.30)
+  rubocop-rails (~> 2.14, >= 2.14.2)
+  sdoc (~> 2.4)
+
+BUNDLED WITH
+   2.3.14

data/LICENSE.txt

@@ -0,0 +1,201 @@
+                                Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2022 Doximity
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,16 @@
+# DUT
+Data Update Tool facilitates efficient bulk-updating of data in Ruby applications
+
+## Installation
+..
+## Usage
+..
+
+## Contributing
+Please read the full [Contributing Guide](CONTRIBUTING.md) with attention and respect the suggestions as well as the
+guidelines from the [Code of Conduct](CODE_OF_CONDUCT.md) when contributing.
+
+[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](CODE_OF_CONDUCT.md)
+
+## License
+The gem is licensed under an Apache 2 license. Contributors are required to sign a contributor license agreement. See [LICENSE.txt](./LICENSE.txt) and [CONTRIBUTING.md](./CONTRIBUTING.md) for more information.

data/Rakefile

@@ -0,0 +1,23 @@
+# frozen_string_literal: true
+
+require File.join("bundler", "gem_tasks")
+require File.join("rspec", "core", "rake_task")
+require "sdoc"
+
+FileList["tasks/*.rake"].each { |task| load task }
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec
+
+RDoc::Task.new do |rdoc|
+  rdoc.main = "README.md"
+  rdoc.markup = "tomdoc"
+  rdoc.options << "--format=sdoc"
+  rdoc.options << "--github --encoding=UTF-8"
+  rdoc.rdoc_dir = "doc"
+  rdoc.rdoc_files.exclude("vendor", "tmp")
+  rdoc.rdoc_files.include("README.md", "lib", "*.rb")
+  rdoc.template = "rails"
+  rdoc.title = "omniauth-doximity Documentation"
+end

data/dut.gemspec

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+require 'English'
+require File.expand_path('lib/dut/version', __dir__)
+
+Gem::Specification.new do |spec|
+  spec.name          = "dut"
+  spec.version       = Dut::VERSION
+  spec.authors       = ["Carlos Gabaldon"]
+  spec.email         = ["cgabaldon@doximity.com"]
+  spec.description   = 'Data Update Tool facilitates efficient bulk-updating of data in Ruby applications'
+  spec.summary       = 'Data Update Tool'
+  spec.homepage      = "https://github.com/doximity/dut.git"
+  spec.license       = "Apache-2.0"
+
+  spec.required_ruby_version = Gem::Requirement.new(">= 2.7.5")
+
+  spec.metadata["homepage_uri"]    = spec.homepage
+  spec.metadata["source_code_uri"] = spec.homepage
+  spec.metadata["changelog_uri"]   = "https://github.com/doximity/dut/blob/master/CHANGELOG.md"
+
+  spec.files         = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 2.3.12"
+  spec.add_development_dependency "rake", '~> 11.2', '>= 11.2.2'
+  spec.add_development_dependency "rspec", '~> 3.11'
+  spec.add_development_dependency "rspec_junit_formatter" # required for the ci raketask
+  spec.add_development_dependency "rubocop", '~> 1.30'
+  spec.add_development_dependency "rubocop-rails", '~> 2.14', '>= 2.14.2'
+  spec.add_development_dependency "sdoc", '~> 2.4'
+end

data/lib/dut/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Dut
+  VERSION = "0.0.1"
+end

data/lib/dut.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+require "dut/version"

data/spec/rubocop_spec.rb

@@ -0,0 +1,9 @@
+# frozen_string_literal: true
+
+require_relative "spec_helper"
+
+describe "Rubocop" do
+  it "should pass with no offenses detected" do
+    expect(`rubocop`).to include("no offenses detected")
+  end
+end

data/spec/spec_helper.rb

@@ -0,0 +1,4 @@
+# frozen_string_literal: true
+
+require File.join("bundler", "setup")
+require "rspec"

data/tasks/ci.rake

@@ -0,0 +1,16 @@
+# frozen_string_literal: true
+
+namespace :ci do
+  desc "Run tests"
+  task :specs do
+    sh "bundle exec rspec --color spec --format progress"
+  end
+
+  desc "Run rubocop"
+  task :rubocop do
+    sh "bundle exec rubocop --display-cop-names --extra-details --display-style-guide"
+  end
+
+  desc "Build documentation"
+  task doc: :rdoc
+end

metadata

@@ -0,0 +1,207 @@
+--- !ruby/object:Gem::Specification
+name: dut
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Carlos Gabaldon
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2022-05-26 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.3.12
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.3.12
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '11.2'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 11.2.2
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '11.2'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 11.2.2
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.11'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.11'
+- !ruby/object:Gem::Dependency
+  name: rspec_junit_formatter
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.30'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.30'
+- !ruby/object:Gem::Dependency
+  name: rubocop-rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.14'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.14.2
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.14'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.14.2
+- !ruby/object:Gem::Dependency
+  name: sdoc
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.4'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.4'
+description: Data Update Tool facilitates efficient bulk-updating of data in Ruby
+  applications
+email:
+- cgabaldon@doximity.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".circleci/config.yml"
+- ".github/CODEOWNERS"
+- ".github/PULL_REQUEST_TEMPLATE.md"
+- ".gitignore"
+- ".rubocop.yml"
+- ".ruby-version"
+- CHANGELOG.md
+- CONTRIBUTING.md
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- dut.gemspec
+- lib/dut.rb
+- lib/dut/version.rb
+- spec/rubocop_spec.rb
+- spec/spec_helper.rb
+- tasks/ci.rake
+- vendor/cache/activesupport-7.0.3.gem
+- vendor/cache/ast-2.4.2.gem
+- vendor/cache/concurrent-ruby-1.1.10.gem
+- vendor/cache/diff-lcs-1.5.0.gem
+- vendor/cache/i18n-1.10.0.gem
+- vendor/cache/minitest-5.15.0.gem
+- vendor/cache/parallel-1.22.1.gem
+- vendor/cache/parser-3.1.2.0.gem
+- vendor/cache/psych-4.0.4.gem
+- vendor/cache/rack-2.2.3.gem
+- vendor/cache/rainbow-3.1.1.gem
+- vendor/cache/rake-11.3.0.gem
+- vendor/cache/rdoc-6.4.0.gem
+- vendor/cache/regexp_parser-2.4.0.gem
+- vendor/cache/rexml-3.2.5.gem
+- vendor/cache/rspec-3.11.0.gem
+- vendor/cache/rspec-core-3.11.0.gem
+- vendor/cache/rspec-expectations-3.11.0.gem
+- vendor/cache/rspec-mocks-3.11.1.gem
+- vendor/cache/rspec-support-3.11.0.gem
+- vendor/cache/rspec_junit_formatter-0.5.1.gem
+- vendor/cache/rubocop-1.30.0.gem
+- vendor/cache/rubocop-ast-1.18.0.gem
+- vendor/cache/rubocop-rails-2.14.2.gem
+- vendor/cache/ruby-progressbar-1.11.0.gem
+- vendor/cache/sdoc-2.4.0.gem
+- vendor/cache/stringio-3.0.2.gem
+- vendor/cache/tzinfo-2.0.4.gem
+- vendor/cache/unicode-display_width-2.1.0.gem
+homepage: https://github.com/doximity/dut.git
+licenses:
+- Apache-2.0
+metadata:
+  homepage_uri: https://github.com/doximity/dut.git
+  source_code_uri: https://github.com/doximity/dut.git
+  changelog_uri: https://github.com/doximity/dut/blob/master/CHANGELOG.md
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.7.5
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.2.32
+signing_key: 
+specification_version: 4
+summary: Data Update Tool
+test_files:
+- spec/rubocop_spec.rb
+- spec/spec_helper.rb