manifolds 0.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +7 -0
- data/.rubocop.yml +10 -0
- data/CHANGELOG.md +5 -0
- data/CODE_OF_CONDUCT.md +84 -0
- data/LICENSE.txt +21 -0
- data/README.md +44 -0
- data/Rakefile +8 -0
- data/docs/CONTRIBUTING.md +33 -0
- data/lib/manifolds/cli.rb +23 -0
- data/lib/manifolds/version.rb +5 -0
- data/lib/manifolds.rb +8 -0
- data/sig/manifolds.rbs +4 -0
- metadata +71 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: ebadfc167043455aa450104c819e5d93e6343a603476eb00ae580ebc5be09bfe
|
4
|
+
data.tar.gz: 7dbfd89a0654939dc3e41c4378d77ee07c07b734f9875d1355ec1f0f8d4a24ff
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 0eb4eb3f35ebec97d3313dd1322321e8cb43cbb30f4980859728c2168392e222c78246a5ea2063d2c075e40f92b092b48a2d6f7cb222d1e222f8213b23ee8600
|
7
|
+
data.tar.gz: b0f23d7b6ffa95005f76c932ab76fb537fe939f8a8b59f866053a77e3ddfd428556e6a05516b278b20f706f6c494c4e6344199792b35e30482958d8f69064a2f
|
data/.rubocop.yml
ADDED
data/CHANGELOG.md
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,84 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
6
|
+
|
7
|
+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
|
8
|
+
|
9
|
+
## Our Standards
|
10
|
+
|
11
|
+
Examples of behavior that contributes to a positive environment for our community include:
|
12
|
+
|
13
|
+
- Demonstrating empathy and kindness toward other people
|
14
|
+
- Being respectful of differing opinions, viewpoints, and experiences
|
15
|
+
- Giving and gracefully accepting constructive feedback
|
16
|
+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
|
17
|
+
- Focusing on what is best not just for us as individuals, but for the overall community
|
18
|
+
|
19
|
+
Examples of unacceptable behavior include:
|
20
|
+
|
21
|
+
- The use of sexualized language or imagery, and sexual attention or
|
22
|
+
advances of any kind
|
23
|
+
- Trolling, insulting or derogatory comments, and personal or political attacks
|
24
|
+
- Public or private harassment
|
25
|
+
- Publishing others' private information, such as a physical or email
|
26
|
+
address, without their explicit permission
|
27
|
+
- Other conduct which could reasonably be considered inappropriate in a
|
28
|
+
professional setting
|
29
|
+
|
30
|
+
## Enforcement Responsibilities
|
31
|
+
|
32
|
+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
|
33
|
+
|
34
|
+
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
|
35
|
+
|
36
|
+
## Scope
|
37
|
+
|
38
|
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
|
39
|
+
|
40
|
+
## Enforcement
|
41
|
+
|
42
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at clayton@bustle.com. All complaints will be reviewed and investigated promptly and fairly.
|
43
|
+
|
44
|
+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
|
45
|
+
|
46
|
+
## Enforcement Guidelines
|
47
|
+
|
48
|
+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
|
49
|
+
|
50
|
+
### 1. Correction
|
51
|
+
|
52
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
|
53
|
+
|
54
|
+
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
|
55
|
+
|
56
|
+
### 2. Warning
|
57
|
+
|
58
|
+
**Community Impact**: A violation through a single incident or series of actions.
|
59
|
+
|
60
|
+
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
|
61
|
+
|
62
|
+
### 3. Temporary Ban
|
63
|
+
|
64
|
+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
|
65
|
+
|
66
|
+
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
|
67
|
+
|
68
|
+
### 4. Permanent Ban
|
69
|
+
|
70
|
+
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
|
71
|
+
|
72
|
+
**Consequence**: A permanent ban from any sort of public interaction within the community.
|
73
|
+
|
74
|
+
## Attribution
|
75
|
+
|
76
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
|
77
|
+
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
78
|
+
|
79
|
+
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
|
80
|
+
|
81
|
+
[homepage]: https://www.contributor-covenant.org
|
82
|
+
|
83
|
+
For answers to common questions about this code of conduct, see the FAQ at
|
84
|
+
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
MIT License
|
2
|
+
|
3
|
+
Copyright (c) 2024 BDG Media, Inc
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
13
|
+
copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
21
|
+
SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,44 @@
|
|
1
|
+

|
2
|
+
|
3
|
+
# Manifolds
|
4
|
+
|
5
|
+
Manifolds is a framework designed to streamline the process of generating and managing data infrastructures in Google BigQuery using Terraform. By leveraging Manifolds, teams can efficiently create complex views that join dimensional data with multiple metrics tables, enabling more dynamic data interactions and fewer sandcastles.
|
6
|
+
|
7
|
+
## Philosophy
|
8
|
+
|
9
|
+
At the heart of Manifolds, our philosophy is to simplify the complexity inherent in managing large-scale data architectures. We aim to provide a tool that not only facilitates the easy setup of data structures but also adheres to best practices in scalability, maintainability, and performance. Manifolds is built for data engineers, by data engineers, ensuring that the nuances and common challenges in data management are well-addressed.
|
10
|
+
|
11
|
+
## Features
|
12
|
+
|
13
|
+
- **Unified Data Modeling**: Manifolds introduces a standardized way to model dimensions and metrics, ensuring consistency and reliability in data reporting and analysis.
|
14
|
+
- **Scalability**: Designed to handle large volumes of data, supporting a variety of data types and structures.
|
15
|
+
- **Flexibility**: Easily adapt to different kinds of metric groupings such as by device type (e.g., desktop, tablet, mobile) with identical metric structures beneath these segmentations.
|
16
|
+
|
17
|
+
## Getting Started
|
18
|
+
|
19
|
+
### Prerequisites
|
20
|
+
|
21
|
+
- Ruby
|
22
|
+
- Terraform
|
23
|
+
- Google Cloud SDK (gcloud)
|
24
|
+
|
25
|
+
### Installation
|
26
|
+
|
27
|
+
1. **Clone the repository**:
|
28
|
+
|
29
|
+
```bash
|
30
|
+
git clone https://github.com/bustle/manifolds.git
|
31
|
+
cd manifolds
|
32
|
+
```
|
33
|
+
|
34
|
+
2. **Setup Terraform**: Ensure that Terraform is installed and configured to interact with your Google Cloud Platform account.
|
35
|
+
|
36
|
+
3. **Configure Your Environment**: Set up your environment variables and credentials to access Google BigQuery and other necessary services.
|
37
|
+
|
38
|
+
## Contributing
|
39
|
+
|
40
|
+
We welcome contributions from the community! Please check out our [contribution guidelines](docs/CONTRIBUTING.md) for more information on how to get involved.
|
41
|
+
|
42
|
+
## License
|
43
|
+
|
44
|
+
Distributed under the MIT License. See LICENSE for more information
|
data/Rakefile
ADDED
@@ -0,0 +1,33 @@
|
|
1
|
+
# Contributing
|
2
|
+
|
3
|
+
We are excited that you are interested in contributing to Manifolds! To maintain the quality of our project, we ask that contributors adhere to the following guidelines:
|
4
|
+
|
5
|
+
## How to Contribute
|
6
|
+
|
7
|
+
- **Familiarize yourself with the project**:
|
8
|
+
Spend some time understanding the codebase, philosophy, and design patterns used in Manifolds. Feel free to ask questions if something is unclear.
|
9
|
+
|
10
|
+
- ** Check the Issues Tracker**:
|
11
|
+
Before creating a new issue, please check the repository's issue tracker to avoid duplicates. If you find an issue you’d like to tackle, comment that you’re working on it.
|
12
|
+
|
13
|
+
- **Fork and Clone the Repository**:
|
14
|
+
Make a fork of the repository, clone it to your machine, and create a new branch for your contribution.
|
15
|
+
|
16
|
+
- **Code Consistency**:
|
17
|
+
Follow the coding style and conventions already used in Manifolds. This includes commenting your code where necessary and adhering to the existing naming conventions and file structure.
|
18
|
+
|
19
|
+
- **Writing Tests**:
|
20
|
+
Add tests that cover the new features or fixes you are introducing. Ensure that all tests pass before submitting a pull request.
|
21
|
+
|
22
|
+
- **Documentation**:
|
23
|
+
Update the README or documentation with details of changes to the interface, additional environment variables, dependencies, or database migrations, etc.
|
24
|
+
|
25
|
+
- **Submit a Pull Request**:
|
26
|
+
Push your changes to your fork and submit a pull request to the main Manifolds repository. Provide a clear description of the problem and solution, including any relevant issue numbers.
|
27
|
+
|
28
|
+
- **Review and Collaborate**:
|
29
|
+
Be open to feedback and make requested modifications to your pull request if needed. Discussion and collaboration often lead to the best solutions.
|
30
|
+
|
31
|
+
## Code of Conduct
|
32
|
+
|
33
|
+
Respect and professionalism are required at all times; harassment or offensive behavior will not be tolerated. By participating, you are expected to uphold this code.
|
@@ -0,0 +1,23 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
3
|
+
require "thor"
|
4
|
+
require "fileutils"
|
5
|
+
|
6
|
+
# CLI provides command line interface functionality
|
7
|
+
# for creating and managing umbrella projects for data management.
|
8
|
+
class CLI < Thor
|
9
|
+
desc "new_umbrella NAME", "Generate a new umbrella project for data management"
|
10
|
+
def new_umbrella(name)
|
11
|
+
directory_path = "./#{name}/projects"
|
12
|
+
FileUtils.mkdir_p(directory_path)
|
13
|
+
puts "Created umbrella project '#{name}' with a projects directory."
|
14
|
+
# Generate Gemfile inside the new umbrella project
|
15
|
+
File.open("./#{name}/Gemfile", "w") do |file|
|
16
|
+
file.puts "source 'https://rubygems.org'"
|
17
|
+
file.puts "gem 'thor'"
|
18
|
+
end
|
19
|
+
puts "Generated Gemfile for the umbrella project."
|
20
|
+
end
|
21
|
+
end
|
22
|
+
|
23
|
+
CLI.start(ARGV) if __FILE__ == $PROGRAM_NAME
|
data/lib/manifolds.rb
ADDED
data/sig/manifolds.rbs
ADDED
metadata
ADDED
@@ -0,0 +1,71 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: manifolds
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.0.1
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- claytongentry
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2024-04-29 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: thor
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - ">="
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '0'
|
20
|
+
type: :runtime
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - ">="
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '0'
|
27
|
+
description:
|
28
|
+
email:
|
29
|
+
- clayton@bustle.com
|
30
|
+
executables: []
|
31
|
+
extensions: []
|
32
|
+
extra_rdoc_files: []
|
33
|
+
files:
|
34
|
+
- ".rubocop.yml"
|
35
|
+
- CHANGELOG.md
|
36
|
+
- CODE_OF_CONDUCT.md
|
37
|
+
- LICENSE.txt
|
38
|
+
- README.md
|
39
|
+
- Rakefile
|
40
|
+
- docs/CONTRIBUTING.md
|
41
|
+
- lib/manifolds.rb
|
42
|
+
- lib/manifolds/cli.rb
|
43
|
+
- lib/manifolds/version.rb
|
44
|
+
- sig/manifolds.rbs
|
45
|
+
homepage: https://github.com/bustle/manifolds
|
46
|
+
licenses:
|
47
|
+
- MIT
|
48
|
+
metadata:
|
49
|
+
homepage_uri: https://github.com/bustle/manifolds
|
50
|
+
source_code_uri: https://github.com/bustle/manifolds
|
51
|
+
changelog_uri: https://github.com/bustle/manifolds/CHANGELOG.md
|
52
|
+
post_install_message:
|
53
|
+
rdoc_options: []
|
54
|
+
require_paths:
|
55
|
+
- lib
|
56
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
57
|
+
requirements:
|
58
|
+
- - ">="
|
59
|
+
- !ruby/object:Gem::Version
|
60
|
+
version: 3.0.0
|
61
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
62
|
+
requirements:
|
63
|
+
- - ">="
|
64
|
+
- !ruby/object:Gem::Version
|
65
|
+
version: '0'
|
66
|
+
requirements: []
|
67
|
+
rubygems_version: 3.4.10
|
68
|
+
signing_key:
|
69
|
+
specification_version: 4
|
70
|
+
summary: A CLI for managing data infrastructures in BigQuery
|
71
|
+
test_files: []
|